Related
I'm trying to build a new version of Apps2SD (version 2.6). I'm trying to get this version compatible with EXT4. I have resurrected my Darktremor Kernel (for those of you who don't know what that is...which is probably almost everyone...this is a kernel I built when the Hero source came out), which has EXT4 support.
I have set my ext partition to be EXT4.
The problem I'm having is, if I use the following command:
mount -o noatime,nodiratime -t auto /dev/block/mmcblk0p2 /system/sd
I get the following errors:
During boot: Invalid argument
In ADB shell: No such device
I've tried using -t ext4, but I just get "No such device".
What am I doing wrong here? I've search all over XDA and the Internet. I see Roms that have EXT4 in them, but nobody talks about how to manually mount one (I can find all sorts of information about EXT3, but it appears the attitude with EXT4 is "it just works.")
Thanks.
tkirton said:
What am I doing wrong here? I've search all over XDA and the Internet. I see Roms that have EXT4 in them, but nobody talks about how to manually mount one (I can find all sorts of information about EXT3, but it appears the attitude with EXT4 is "it just works.")
Thanks.
Click to expand...
Click to collapse
I wish I could help, but I haven't messed around with the kernel or even EXT4... hmm, maybe it's time for me to start! You have any specific tutorials you'd recommend tkirton?
pseudoremora said:
I wish I could help, but I haven't messed around with the kernel or even EXT4... hmm, maybe it's time for me to start! You have any specific tutorials you'd recommend tkirton?
Click to expand...
Click to collapse
I have a guide on how to compile your own kernel. The same guide is one of the threads in XDA, but I know how hard it is sometimes to search for something (hence why I'm asking about EXT4)
http://www.darktremor.com/kernels.html
See if that helps as a starting document.
Sorry that I having nothing useful to offer on this subject. However, am I assuming correctly that current recovery images would support an EXT4 when doing Nandroid backups for A2SD users?
Ceger
tkirton said:
I have a guide on how to compile your own kernel. The same guide is one of the threads in XDA, but I know how hard it is sometimes to search for something (hence why I'm asking about EXT4)
http://www.darktremor.com/kernels.html
See if that helps as a starting document.
Click to expand...
Click to collapse
****, I probably should have searched, I'm sure I would have found it. Thanks though, definitely going to take a look at this!
Ceger said:
Sorry that I having nothing useful to offer on this subject. However, am I assuming correctly that current recovery images would support an EXT4 when doing Nandroid backups for A2SD users?
Ceger
Click to expand...
Click to collapse
Honestly I never tried to backup or restore on an EXT4 drive. I'm sure it will work, but I'm suspecting there's issues with the kernel source. I never had a reason to go to EXT4 (EXT3 suited my needs just fine and there aren't a lot of Roms that support EXT4).
tkirton said:
Honestly I never tried to backup or restore on an EXT4 drive. I'm sure it will work, but I'm suspecting there's issues with the kernel source. I never had a reason to go to EXT4 (EXT3 suited my needs just fine and there aren't a lot of Roms that support EXT4).
Click to expand...
Click to collapse
I'll ask Toast and Fresh as their Dev ROM supports EXT4, so they should know if Nandroid backs that up or not... I suppose.
Ceger
Ceger said:
I'll ask Toast and Fresh as their Dev ROM supports EXT4, so they should know if Nandroid backs that up or not... I suppose.
Ceger
Click to expand...
Click to collapse
I'm not doubting it does...Amon_RA stated in several threads that it does. But that kernel and the one used to boot are completely different. The problem I'm running into is the one for boot (the 1.5 kernel, or version 2.6.27 of the kernel). It won't activate there, although there is an entry called /dev/block/mmcblk0p2 (so the kernel does see something...it just won't mount).
Maybe the issue is busybox. I'll see if I can find busybox on the recovery kernel and port it.
I was thinking it could be because .27 uses ext4-dev. I've seen a gang load of ext4 patches for .27 I used the rename patch in my kernel. But it seems not to work. When testing it I thought it did work. As a2sd in our init.d was seeming to be working and I had all my apps. But after everyone was saying they couldn't get it to work, I'm thinking I may need to try another patch. But yeah I'm not sure what the issue is. Maybe we can contact cyanogen or amon on this as I know they get it to work somehow.
toastcfh said:
I was thinking it could be because .27 uses ext4-dev. I've seen a gang load of ext4 patches for .27 I used the rename patch in my kernel. But it seems not to work. When testing it I thought it did work. As a2sd in our init.d was seeming to be working and I had all my apps. But after everyone was saying they couldn't get it to work, I'm thinking I may need to try another patch. But yeah I'm not sure what the issue is. Maybe we can contact cyanogen or amon on this as I know they get it to work somehow.
Click to expand...
Click to collapse
I'm coming up with the same conclusion...the ext4dev drivers don't appear to work. They load up (I'm getting that from a device dump), but they won't mount. Apparently, it won't mount in recovery, either.
I'm wondering if I grab a 1.6 or better source if I can recompile the part for ext4 inside the rest of the Hero 1.5 source. If I remember correctly with Linux compiling, as long as I have the correct dependencies, I should be able to compile it.
Hello - I am attempting to connect to a cisco vpn using the instructions here but have run into a "common" problem- I copied a post over on the EVO forum- I have exactly the same problem- could some one help me out to compile a tun.ko that is compatible with the current stock kernel- thanks in advance!!! The instructions are found here
I am attempting to get vpnc (for cisco vpn) working on the epic but have run into a snag getting the tun.ko module loaded. When I attempt to insmod tun.ko I get exec format error and dmesg yields
tun: version magic '2.6.32.9-27220-g328f560 preempt mod_unload ARMv7 ' should be '2.6.29-a2443432 preempt mod_unload ARMv7 '
I found an excellent post (#12) by sjakub at hxxp://forum.xda-developers.com/showthread.php?t=630703&page=2
which describes step by step how to overcome this but unfortunately I have no access to linux in order to attempt this myself.
Would anyone be kind enough to compile the proper file for please?
Thanks very much.
Click to expand...
Click to collapse
jimmyz said:
could some one help me out to compile a tun.ko that is compatible with the current stock kernel
Click to expand...
Click to collapse
Does this work?
Mirror link (does not require forum login):
tun-DI18.zip
Thanks- will try it a soon as I get home!
EDIT: I did not receive any errors with your file- I will report back as soon as I try to connect to VPN!
Sent from my SPH-D700 using XDA App
I was able to insmod it, but my modem is down at home so I can't start my VPN.
I'll be jumping for joy if this works, I beat my head against the wall trying to find a good tun.ko for DI18 a few days back.
And I'm tunneled in. Seems to be working but I'm having trouble getting my traffic to route right so far, but I doubt that's related to the tun.ko.
Thanks a ton!
Hemick said:
And I'm tunneled in. Seems to be working but I'm having trouble getting my traffic to route right so far, but I doubt that's related to the tun.ko.
Thanks a ton!
Click to expand...
Click to collapse
what version of the VPN connections are you using? Could you find it on the market?
mkasick said:
Does this work?
Click to expand...
Click to collapse
Mkasick- thanks again for the tun.ko!!! After some troubleshooting (I needed to append a domain setting) I got it to work!!!!!
Can you please set up a way to donate to you- I would like to buy you a beer! I was going to ask for a kernel that automatically loads tun.ko but the vpn_connections apk seems to do it automatically
thanks again for you help!!!!
jimmyz said:
Can you please set up a way to donate to you- I would like to buy you a beer!
Click to expand...
Click to collapse
I appreciate the gratitude. Unfortunately I think it would take me far longer to figure out how to setup donations than it did to compile the module. So, in the meantime, enjoy a beer yourself as a "thanks" to me.
Thank you for this
I have been waiting for this too. Now I need to generate an OpenVPN configuration for our ssl VPN.
I registered just so I could download this module.
I must be doing something wrong because when I try to insmod I get init_module 'tun.ko' failed (Exec format error). I'm at 2.1-update1, 2.6.29, and SPH-D700 ECLAIR.DI18 so guess I'm not holding my mouth right.
flash_c4 said:
I must be doing something wrong because when I try to insmod I get init_module 'tun.ko' failed (Exec format error). I'm at 2.1-update1, 2.6.29, and SPH-D700 ECLAIR.DI18 so guess I'm not holding my mouth right.
Click to expand...
Click to collapse
I decided to try and copy the file over again and this time it worked so something must have happened during the transfer the first time.
How does one "install" this module? I have the Xtreme 1.0.1 kernel and I ran "insmod -v tun.ko" and it seems to stop the FC on the cisco ipsec vpn. But the module does not survive a reboot. I'm guessing I need to recompile it into the kernel? Can someone post some steps on how to do that?
Also, when using the vpn, after hitting connect, it immediately says failed. I'm not sure if that's because I didn't get tun.ko installed correctly, or just bad credential.
you all rock
first time poster, short time lurker...just started flashing my droid a few weeks ago, and am now also playing with an epic.
just wanted to comment on how much i liked this thread, even though i understand, uh, not much of it. you all rock! keep up the open source mentality and for my part i'll keep purchasing/donating for things i enjoy using. And hefting beers for all of you
jimmyz said:
Mkasick- thanks again for the tun.ko!!! After some troubleshooting (I needed to append a domain setting) I got it to work!!!!!
Can you please set up a way to donate to you- I would like to buy you a beer! I was going to ask for a kernel that automatically loads tun.ko but the vpn_connections apk seems to do it automatically
thanks again for you help!!!!
Click to expand...
Click to collapse
droid is currently running UD 2.0 with Chevy 1.25 low voltage kernel - fast and awesome!! quadrant in the 1100s
epic currently using syndicate fully loaded 1.0.2 but also tried and liked the froyo betas... quadrant = 1207
Kernel module
Having the tun.ko file alone might not work. For example, I have a Desire HD. I extracted the kernel config from /proc/config.gz and saw that the TUN/TAP module was not even included in the kernel as a module (M). Correct me if I'm wrong but if the kernel isn't even compiled for support for a module, the module will not load even if you try to load the tun.ko module using insmod/modprobe. Your kernel either needs to have the module selected as (M) or (Y) - if you want it buit-in.
Therefore, I had to:
(1) grab the Desire HD sources from http://developer.htc.com
(2) extract the config for that kernel from /proc/config.gz
(3) Also get hold of the android ndk compiler for x-platform compilation for the arm architecture.
(4) compile the kernel sources using that config file in (2) but also with support for tun.ko as a module (m). You can do this with the command 'make menuconfig' in the kernel sources dir. The kernel sources I grabbed from the url above from htc seemed to have a few files missing. One of them was the ntrig.c file, which I got from the main android kernel sources instead.
(5) Once I got them compiled, this generated the kernel as bZimage a few modules (including tun.ko).
(6) For me the next issue was to get the kernel on my device because unless you have a bootloader than ignores signatures on the kernel, you won't be able to upload your new kernel.
(7) I flashed my bootloader to clockworkmod. Used this guide: http://forum.xda-developers.com/showthread.php?t=805327
(8) once i unlocked the bootloader I issued a 'fastboot flash zimage zImage' (my compiled version of the kernel)
(9) Uploaded the tun.ko too and did an insmod to loads tun.ko and it worked.
rcboosted said:
How does one "install" this module?
Click to expand...
Click to collapse
You don't, you have to "insmod" it on every reboot.
rcboosted said:
I'm guessing I need to recompile it into the kernel?
Click to expand...
Click to collapse
You can compile a kernel with the tun driver built-in, so you don't need to rely on an external module. But it's tougher to keep up with kernel updates that way. Ask in the thread of your favorite kernel where to obtain the source and instructions for compiling it.
shakeup said:
Correct me if I'm wrong but if the kernel isn't even compiled for support for a module, the module will not load even if you try to load the tun.ko module using insmod/modprobe. Your kernel either needs to have the module selected as (M) or (Y) - if you want it buit-in.
Click to expand...
Click to collapse
That's not the case. The kernel does need to be compiled with general module support, but this will always be the case since the Epic uses a fair number of proprietary driver modules.
Setting a particular driver to be compiled as a module (=m) in the kernel config simply means the module, and any of its dependencies, are built alongside the kernel. The kernel itself is the same in either case, unless the module requires a kernel option/driver that can't be compiled as a module, which is rare these days, but was more common in Linux 2.4 and earlier.
In any event, the tun.ko posted here does work with stock DI18.
Edit: There is an issue when you try to compile a driver module that requires an option to be enabled in a different driver that's built-in to the kernel you're using but is currently disabled. I can't think of a good example of such at the moment, but I think I have ran into it in the past.
It's obvious I'm no linux or android expert by any means. I have no clue how to compile a kernel or recompile a module. So all this talk about recompiling is way over my head.
I'm just trying to connect to a IPSec vpn server using vpnc client (http://code.google.com/p/get-a-robot-vpnc/). Currently running Epic Experience rom and the latest Xtreme kernel. Everytime I tried to connect, it fails immediately. I've verified my credentials are correct, so I don't know what else I can do except wait for CM 6 to come out for the Epic.
rcboosted said:
Everytime I tried to connect, it fails immediately.
Click to expand...
Click to collapse
I'm not familiar with that particular program, but you can get a better idea of what's going wrong with a logcat dump.
For example, your credentials might be correct, but your phone might still have difficulty resolving the server, negotiating the connection, etc.
Thanks for the help. I tried logcat and the authentication part seems to be ok, this is what happens after the authentication:
D/VPN_Connections(29594): done interacting with vpnc
D/VPN_Connections(29594): process stderr:
D/VPN_Connections(29594): Read vpnc process line as null
D/VPN_Connections(29594): Attempt to read vpnc process id did not return anything
D/VPN_Connections(29594): process had died, return as failed connection
It doesn't tell me much, but maybe it means something to you.
rcboosted said:
It's obvious I'm no linux or android expert by any means. I have no clue how to compile a kernel or recompile a module. So all this talk about recompiling is way over my head.
I'm just trying to connect to a IPSec vpn server using vpnc client (http:/9/code.google.com/p/get-a-robot-vpnc/). Currently running Epic Experience rom and the latest Xtreme kernel. Everytime I tried to connect, it fails immediately. I've verified my credentials are correct, so I don't know what else I can do except wait for CM 6 to come out for the Epic.
Click to expand...
Click to collapse
I would guess you need a tun.ko specifically for that kernel you are using (Xtreme)- maybe its best to go back to stock- use the tun.ko in this thread and see if you can get it to work?
I just followed this article to run ubuntu on my nexus s with CM7 running on it.
but each time I typing "bootubuntu"
I got this error:
mount: mounting /dev/loop1 on /data/local/ubuntu failed: Invalid argument
This error should happen when executing this line in bootubuntu:
mount -t ext2 /dev/block/loop1 /data/local/ubuntu
Any ideas ?
Are you sure that the kernel you are using supports the ext2 filesystem and loopback device?
Last lines of "dmesg" command might be helpful (if it exists).
how-to-install-ubuntu-on-your-android
This is the article I followed.
I'm not sure whether CM7 support ext2 and loop device, but I see somewhere people said they run ubuntu on CM7 successfully, that's why I post this thread and hope someone can confirm it and show me the steps.
Or let me know your experience on how to run Ubuntu on nexus s.
I like the busybox way to run ubuntu, means if I run a native ubuntu, I can't use my phone feature anymore.
If you read this: http://androlinux.com/android-ubuntu-development/how-to-install-ubuntu-on-android/
Just a few lines into the text there is this paragraph:
For example, G2 Phone and Nexus One both come with loop device support so there’s no need for us to compile a new kernel for it but for others, you may have to.
Click to expand...
Click to collapse
I don't know whether the cm7 kernel kernel supports loop either, but there are many kernels floating around this forum. Maybe one of them does.
Thanks man.
Finally I figure this out. When I got this phone, the seller had already pre-installed a rooted CM7 and busybox. That may cause the problem.
After I re-install the busybox with the latest version, it works.
So CM7 and Nexus S are good to run Ubuntu.
Thanks for taking your time once again.
Hi all,
Have any of you been able to get a Cifs share mounted under android 4.3 on the N10.
I've tried various kernels and managers like Cifs manager but with no joy, they complain of invalid argument.
It seems like there has been success on the N7 according to this thread http://forum.xda-developers.com/showthread.php?t=2107224&page=7 but I can't see anything for the N10.
If it does work for you could you let me know what ROM / Kernel combo you use?
Not only 4.3. I haven't managed to make it work on 4.2.2 either
Sent from my GT-I9505 using Tapatalk 4
http://forum.xda-developers.com/showthread.php?t=2430056
^^^^^^^ What zod said. Working fine for me
I tried several combinations to mount CIFS shares with mountmanager:
Trinity + Carbon Rom, Sentinel, CM10.2 = works without problems
Flaming Monkey + Carbon Rom, Sentinel, CM10.2 = works - but without UTF-8 (for special characters like öäü...)
KTManta + Carbon Rom, Sentinel, CM10.2 = doesnt work.
Any Kernel + Purity Rom, AOKP, PA = doesn't work.
Could someone please confirm if CIFS is finally dead on Android? I haven't seen a single user manage to make it work. I even asked kernel developers to patch their kernel with this only solution provided here and even though they were happy in the beginning they never wanted to talk about it later which makes me think it was a hell or them.
I'd really like to know if I should just uninstall all CIFS related staff and just forget about it.
Edit:
Sorry I think it's wrong threat
andreasy said:
Could someone please confirm if CIFS is finally dead on Android? I haven't seen a single user manage to make it work. I even asked kernel developers to patch their kernel with this only solution provided here and even though they were happy in the beginning they never wanted to talk about it later which makes me think it was a hell or them.
I'd really like to know if I should just uninstall all CIFS related staff and just forget about it.
Edit:
Sorry I think it's wrong threat
Click to expand...
Click to collapse
Google sure seems to be trying really hard to kill CIFS (and any network filesystems for that matter) on Android. As it stands now (in 4.3) there is no possible way to get CIFS working properly on the stock ROMs with a stock kernel. This is because the geniuses at Google removed loadable module support from the stock kernel and because of the way they implemented the multi-user stuff (using filesystem namespaces). The thing that kills me is that there is absolutely no reason for Google to make this so difficult. They could have simply compiled support for network filesystems into the kernel if they wanted to remove modules for "security". It would also be trivial for them to add a mount point which propagates to the user namespaces. They did this crap on purpose. And that is exactly the reason why my next tablet will not be an Android one. You shouldn't have to hack your tablet to get basic functionality that should just work out of the box. I'm done being scroogled.
Anyhow, I did manage to get CIFS working on my Nexus 7 which is running 4.3. See my post here for details. Now, I don't think my kernel will work on your Nexus 10. But, if you flash someone else's custom kernel (or compile your own) for the Nexus 10 which does have CIFS support/modules you should be able to use my update.zip which does not contain the kernel. I don't have a Nexus 10 to test on, so I can't promise anything but I don't see why it wouldn't work.
With new 4.3.1 Rom Versions I have troubles with CIFS Mount.
I can mount my NAS without problems with Terminal command, and I can see all mounted Files and Folders in Terminal.
But any App (like ES Fileexplorer, Solidexplorer, Power-Amp....) can't see any files. The Folder always keeps empty.
I have tried several mount points: /sdcard/cifs, storage/emulated/legacy/cifs, /data/media/cifs. Always the mount is visible in Terminal but not in all apps.
I have tried many mount options like: noperm, rw, file_mode, dir_mod, gid.....
cien12 said:
With new 4.3.1 Rom Versions I have troubles with CIFS Mount.
I can mount my NAS without problems with Terminal command, and I can see all mounted Files and Folders in Terminal.
But any App (like ES Fileexplorer, Solidexplorer, Power-Amp....) can't see any files. The Folder always keeps empty.
I have tried several mount points: /sdcard/cifs, storage/emulated/legacy/cifs, /data/media/cifs. Always the mount is visible in Terminal but not in all apps.
I have tried many mount options like: noperm, rw, file_mode, dir_mod, gid.....
Click to expand...
Click to collapse
Hi there, could you post the command line you use to mount your NAS drive ? I keep getting "Invalid argument", this is what I've tried
Code:
mount -t cifs //192.168.1.3/music /mnt/music
pkfox said:
Hi there, could you post the command line you use to mount your NAS drive ? I keep getting "Invalid argument", this is what I've tried
Code:
mount -t cifs //192.168.1.3/music /mnt/music
Click to expand...
Click to collapse
You have to get su access first with "su"
mount -r -o noperm,rw,file_mode=0777,dir_mode=0777,uid=1000,gid=1000,unc=\\\\192.168.0.10\\music,username=***,password=*** -t cifs none /sdcard/cifs
Thanks that worked, do you know of a way to mount automatically at boot time on Android ? I notice there is no /etc/fstab
Thanks again.
Hi all, if your goal is simply to play music and video from your NAS to your android device, you can use Kodi (xbmc) that can access cifs path directly!
Hey everyone. I bought this device specifically because I do a lot of work on linux in command line world and I though it would be the perfect device when combined with the Logitech Pro keyboard and Complete Linux Installer (it's an app on Google Play). It turned out to be quite a bit of work getting everything working because of Knox and SELinux. Eventually I got a custom kernel working that allows me to toggle SELinux between permissive and enforcing.
I attached an Odin flashable tar that works on the SM-P900 (wifi version). I am on the North American version, so I have no idea whether it will work in other regions. If you flash this kernel then there are a few things you need to know:
I'm assuming you already have root on your device.
When you boot it will still be in "Enforcing" mode. This change simply allows you to use the "setenforce" terminal command or any of the apps on Google Play that do this for you.
You might experience some wifi weirdness after you flash the kernel. You just need to open up /system/build.prop and change ro.securestorage.support from true to false and then reboot to resolve the issue.
If you have a different version of the device or want to compile it yourself for any reason I wrote an article describing how I compiled it here:
http://graemehill.ca/compiling-permissive-android-kernel/
I also did a few other things to fix the keyboard and get linux running properly, so if you're interested in that I described my setup in more detail here:
http://graemehill.ca/turning-a-galaxy-note-pro-into-a-linux-laptop/
Thank you for this!
Sent from my SM-P900 using Tapatalk
trying to build kernel
I'm trying to follow your guide to compile a kernel from source. I have installed (on my Win 8.1_64 PC) Android SDK/NDK. GnuWin32, JavaJRE, and downloaded SM-P900 kernel source.
I'm getting errors at "Apply Kernel Config" step.
here's the output: http://pastebin.com/yFqDrNY8
Thanks for your help
Don :good:
dodo99x said:
I'm trying to follow your guide to compile a kernel from source. I have installed (on my Win 8.1_64 PC) Android SDK/NDK. GnuWin32, JavaJRE, and downloaded SM-P900 kernel source.
I'm getting errors at "Apply Kernel Config" step.
here's the output: http://pastebin.com/yFqDrNY8
Thanks for your help
Don :good:
Click to expand...
Click to collapse
It looks like you're in Windows. To my knowledge it is not possible to compile a Linux kernel in windows. I would recommend downloading virtual box and installing some Linux distro in there. This is what I was talking about in the "environment" section at the top of the article.
For android development I find that you need access to a lot of tools where some are only available on Windows and others are only available on Linux so a Windows PC with a Linux VM is ideal in my opinion.
Oh ok, no problem. I just misread the guide. I've setup a build environment in a vm before to compile aosp for my Nexus 10. Shouldn't be too hard to do it again. I recently rebuilt my pc so the vm I had got nuked.
Sent from my SM-P900 using Tapatalk
ok I got my Ubuntu VM up and running using this guide
http://forum.xda-developers.com/showpost.php?p=50748836&postcount=25
installed android NDK to ~android/NDK, and unzipped the kernel source to ~android/kernel
followed your guide to build a SELinux permissive kernel but i'm getting some errors when trying to compile. here's the output:
http://pastebin.com/Npdu7J5h
EDIT: retried doing the EXPORT command and now it seems to be compiling
dodo99x said:
EDIT: retried doing the EXPORT command and now it seems to be compiling
Click to expand...
Click to collapse
When you export a variable in the terminal it only exists for that one session, so if you open a new terminal instance you need to run the command again. If you want to set it permanently normally you can just put the export command into ~/.bashrc
Oh I see. I'll give that a try. I was able to create a new boot.img following the rest of your guide. I have yet to try flashing it though. Will have to find some info about all the kernel options that can be set. Hopefully be able to integrate HMP to get all eight cores running at the same time.
Sent from my SM-P900 using Tapatalk
Cool, let us know how that goes. I wonder how much it would affect battery life.
Graeme H said:
Hey everyone. I bought this device specifically because I do a lot of work on linux in command line world and I though it would be the perfect device when combined with the Logitech Pro keyboard and Complete Linux Installer (it's an app on Google Play). It turned out to be quite a bit of work getting everything working because of Knox and SELinux. Eventually I got a custom kernel working that allows me to toggle SELinux between permissive and enforcing.
I attached an Odin flashable tar that works on the SM-P900 (wifi version). I am on the North American version, so I have no idea whether it will work in other regions. If you flash this kernel then there are a few things you need to know:
I'm assuming you already have root on your device.
When you boot it will still be in "Enforcing" mode. This change simply allows you to use the "setenforce" terminal command or any of the apps on Google Play that do this for you.
You might experience some wifi weirdness after you flash the kernel. You just need to open up /system/build.prop and change ro.securestorage.support from true to false and then reboot to resolve the issue.
If you have a different version of the device or want to compile it yourself for any reason I wrote an article describing how I compiled it here:
http://graemehill.ca/compiling-permissive-android-kernel/
I also did a few other things to fix the keyboard and get linux running properly, so if you're interested in that I described my setup in more detail here:
http://graemehill.ca/turning-a-galaxy-note-pro-into-a-linux-laptop/
Click to expand...
Click to collapse
I tried to install this using VBox Odin and I couldnt get it to work. Tried using BOOTLOADER and also PDA. Not sure the correct one but neither worked for me. Also, Moblie ODin hasnt yet worked but when it does, things will be much easier for me at least.
I have a newly rooted SM-900. I will have to find time someday to compile the kernel against what I have. Must be a slightly newer version than the one you posted. That is only thing I can think since I just got my 12.2. Thanks for the detailed info.
Camera?
Hey, thanks for the great kernel. It's working as expected to enable permissive mode, but I'm having one issue with it. When I use your kernel, the camera is disabled (says something like "Camera Failed"), and it won't work even when trying different software besides stock, like Google Camera. Anyway, clearing cache, etc. doesn't do anything, but the camera works again when I flash the stock kernel. Is this related to permissive mode or something else with the settings?
aarstar said:
Hey, thanks for the great kernel. It's working as expected to enable permissive mode, but I'm having one issue with it. When I use your kernel, the camera is disabled (says something like "Camera Failed"), and it won't work even when trying different software besides stock, like Google Camera. Anyway, clearing cache, etc. doesn't do anything, but the camera works again when I flash the stock kernel. Is this related to permissive mode or something else with the settings?
Click to expand...
Click to collapse
The camera fails for me too. I dumped a logcat and isolated the issue here:
W/ActivityManager( 2746): Permission Denial: get/set setting for user asks to run as user -2 but is calling from user 0; this requires android.permission.INTERACT_ACROSS_USERS_FULL
V/ApplicationPolicy( 2746): isApplicationStateBlocked userId 0 pkgname com.google.android.GoogleCamera
But... the camera is not a huge deal. It did, however, break wifi. I did not get a logcat of that yet, but I would assume it is also a permission issue.
Wifi works for me using the fix mentioned in the OP. Also, thanks for looking into the camera issue. I agree it's not a big deal, and it's easily fixed by flashing the stock kernel, until someone figures out a proper fix.
aarstar said:
Wifi works for me using the fix mentioned in the OP. Also, thanks for looking into the camera issue. I agree it's not a big deal, and it's easily fixed by flashing the stock kernel, until someone figures out a proper fix.
Click to expand...
Click to collapse
Wow, I totally missed that entire line in the OP... You literally just made my whole day. I fought this all day long, desperate to get ubuntu working. Thank you for pointing that out.
I get "xt_mark.h" is missing (no such file or directory) error. Any idea why that may be?
I'm using the source for p900 international hoping that I may sidestep the camera issue that way (by enabling permissive to the international kernel I mean), but as it stands it does not compile.
I've googled it but until now it was/is to no avail...
Graeme H said:
Hey everyone. I bought this device specifically because I do a lot of work on linux in command line world and I though it would be the perfect device when combined with the Logitech Pro keyboard and Complete Linux Installer (it's an app on Google Play).
Click to expand...
Click to collapse
Hey Graeme H,
we both have the same intention. I am downloading the international Kernel at the moment and will compile it again for you guys. The download takes a little longer as I am at vacations.
I am going this route: doviak.net/debian-kit/debian-kit_p00.html . In the future I would like to have arch linux running on this device but a customized debian would be okay for the beginning, too.
Eventually I will try to use framebuffer instead of vnc or something like that. I would love to use sublime-text and dwm on that device with that resolution
Good luck guys. I will try to update.
Edit: hehe I have dwm in front of me now and the resolution is so high that I am barely able to read
Compiled the kernel and flashed in on my device but my camera is still not working. Maybe we need to edit the config:
# Camera sensor devices
#
# CONFIG_VIDEO_OV7670 is not set
# CONFIG_VIDEO_VS6624 is not set
# CONFIG_VIDEO_MT9M032 is not set
# CONFIG_VIDEO_MT9P031 is not set
# CONFIG_VIDEO_MT9T001 is not set
# CONFIG_VIDEO_MT9V011 is not set
# CONFIG_VIDEO_MT9V032 is not set
# CONFIG_VIDEO_TCM825X is not set
# CONFIG_VIDEO_SR030PC30 is not set
# CONFIG_VIDEO_NOON010PC30 is not set
CONFIG_VIDEO_S5K6B2=y
# CONFIG_S5K6B2_CSI_C is not set
CONFIG_S5K6B2_CSI_D=y
CONFIG_S5K6B2_POSITION_FRONT=y
# CONFIG_S5K6B2_POSITION_REAR is not set
CONFIG_VISION_MODE=y
# CONFIG_VIDEO_M5MOLS is not set
# CONFIG_VIDEO_S5K6AA is not set
Click to expand...
Click to collapse
Rather than each people compiles its kernel, could someone put a link to download the international kernel compiled? I think this would allow more people to get this kernel. Thank
PHP:
smylion said:
Rather than each people compiles its kernel, could someone put a link to download the international kernel compiled? I think this would allow more people to get this kernel. Thank
Click to expand...
Click to collapse
Compiled from Kitkat source. [ur#l]erhan.es/upload/sm-p900-permissive-intl.tar[/url] (odin)
Thank you but the link does not work
smylion said:
Thank you but the link does not work
Click to expand...
Click to collapse
Sorry, it is erhan.es/upload/sm-p900-intl-permissive.tar