I am using this kernel since a while and have been happy with it. Now I discovered that EDS (application to mount encrypted truecrypt compatible containers) seems to mount the containers read-only. I suppose that it might be due to missing fuse support of the kernel (see sovworks.com). Do the custom kernels (and particular optimus prime) usually include the fuse module or are my suspicions correct?
To answer my own question: EDS works. The problems I had seem to come from a broken container. This can seemingly happen if the phone is shut down improperly.
Related
I'm really looking for an app that I can use to SSHFS essentially, so that I can sorta' use a mounted remote dir as an extension of my phones storage, much like you would do in normal, every-day linux.
Is there such a thing? To date, I have not been able to find anything...
You would first need to get Fuse working with the kernel. If/once we can boot custom kernels, it's possible one might ship with Fuse enabled but according to
http://groups.google.com/group/android-kernel/browse_thread/thread/096dda136ce772cb
stock does not have Fuse. Stock does support modules though and I'm fairly sure you can compile Fuse as a module. You'd need to get ahold of the Droid 3 stock kernel source, cross compile a module for Arm and try and get it to not kernel panic the phone. Once you have Fuse in there, it shouldn't be too bad to build a copy of sshfs.
In the mean time, I have found https://market.android.com/details?id=nextapp.fx to be an incredible file manager that support SSH, SMB, and FTP. The only thing missing would be root.
Anyway, I think Fuse support would be awesome but don't have time to work on it at the moment. Do we have the D3 kernel source somewhere?
Naex said:
You would first need to get Fuse working with the kernel. If/once we can boot custom kernels, it's possible one might ship with Fuse enabled but according to
http://groups.google.com/group/android-kernel/browse_thread/thread/096dda136ce772cb
stock does not have Fuse. Stock does support modules though and I'm fairly sure you can compile Fuse as a module. You'd need to get ahold of the Droid 3 stock kernel source, cross compile a module for Arm and try and get it to not kernel panic the phone. Once you have Fuse in there, it shouldn't be too bad to build a copy of sshfs.
In the mean time, I have found https://market.android.com/details?id=nextapp.fx to be an incredible file manager that support SSH, SMB, and FTP. The only thing missing would be root.
Anyway, I think Fuse support would be awesome but don't have time to work on it at the moment. Do we have the D3 kernel source somewhere?
Click to expand...
Click to collapse
Yes, D3 source has been released. There's a thread on it here on XDA in the dev section. Thank's for the info!
Hello everyone,
I am trying to create a CWM flashable zip that will disable the charge led. My wife hates the led shinning all night long on the bedside table.
Consider this a 1.0 version that does not work.
Any help correcting the zips would be greatly appreciated!
http://dl.dropbox.com/u/56179974/Disable green charge LED.zip
http://dl.dropbox.com/u/56179974/Disable red charge LED.zip
http://dl.dropbox.com/u/56179974/Enable charge LEDs.zip
Thanks!
You shouldnt be modifying /sys files in that manner, you should be echoing values into them via a script.
Unfortunately there's no particularly reliable way of execing scripts on boot,
not all the kernels have the init script or install-recovery.sh
Depending on the kernel you could plug the entries into that and have them feed values into /sys
Edit: /sys is a virtual filesystem, it gets built on boot at every boot. You cant write to it during recovery as it disappears when you reboot.
What would be a good kernel to try?
From what I gather I could for instance use a terminal emulator to change the value or I could modify the init script to apply the value at boot?
It's not the kernel specifically, it's the ramdisk it includes.
Here's a quick rundown of how booting works:
Device is powered on -> bootloader starts loading kernel -> kernel loads ramdisk -> ramdisk scripts start loading android core -> boot time scripts and services are loaded
Dell devices have an init.device.post-boot.sh (or something along those lines), but a quick peek though the stock 5xx ramdisk shows that it's not enabled in it (I believe)
They also have flash-recovery.sh, but it might be missing in the HS kernels, so it's the same situtation.
I'd say the simplest way is to make them in scripts and just use a script pharser (like gscript) and load them that way.
Otherwise you would need ramdisk mods and reflash the kernel with the new ramdisk that lets you load more scripts at boot.
/data, /cache, and /system are mounted
/dev and /sys are spawned as they're virtual FS's containing telemetry from the kernel.
Thank you again for the useful information!
When you say "the stock 5xx ramdisk shows that it's not enabled in it (I believe)" does that mean that the init scripts are inaccessible after boot? I am working with the devs on getting Boot Manager working for the DS7 and we keep running into issues building the file system.
The ramdisk has a whitelist of scripts to exec:
The init.<device>.post-boot.sh script was added by dell in most kernels, they simply didnt add it into the stock 5xx ramdisks as they didnt have anything to put into them apparently.
If you check init.<device>.rc or init.rc on "/", look for these two entries:
Code:
service streak-post-boot /system/bin/sh /system/etc/init.streak.post_boot.sh
user root
disabled
oneshot
and
Code:
on property:init.svc.bootanim=stopped
start streak-post-boot
As it demonstrates, it feeds /system/etc/init.streak.post_boot.sh to sh when the boot animation has completed.
But they removed those entries from the stock 5xx ramdisk, they're simply not there anymore.
It still loads /system/etc/install-recovery.sh, you could use that as it does get loaded by the stock kernel.
At least on my rom the file doesnt exist at all, so you could simply replace it.
But if you were to do that the right thing to do is simply have the user modify it themselves, if they already have one with things they added. (this isnt that likely though)
Thanks again TheManii!
I would be working on this but unfortunately my DS7 bent a pin so as of now it is out of commission
I have new connectors on order (10 pack was the minimum) so I am hoping to have it going again soon
why not just implement duct-tape over the light? low-tech solution to your high-tech approach
Because that wouldn't involve me learning to code, etc
Too bad it isn't a problem now anyway considering my DS7 is a goner....
Wetzel402 said:
Because that wouldn't involve me learning to code, etc
Too bad it isn't a problem now anyway considering my DS7 is a goner....
Click to expand...
Click to collapse
check batterystats.bin, it might be related, didnt get a good look at it with my battery dying on the train home
I would but as I stated my DS7 took a dive. The charging port bent a pin and is now shot. A parts tablet on ebay maybe....
Wetzel402 said:
I would but as I stated my DS7 took a dive. The charging port bent a pin and is now shot. A parts tablet on ebay maybe....
Click to expand...
Click to collapse
How much would you want for parts?
PM sent
suggest removing block "# Eric Liu+" -> "# Eric Liu-" in init.rc might help those who are still using their S7.. the nexus7 probably stole the interest though
Anything proceeded with a "#" is a comment and doesnt do anything
Hi,
does the HTC One has CIFS support?
So that the CifsManager can be used on a rooted device?
THX
Well the app is showing as compatible on the Play Store, so I'd presume so.
No it does not.
Just because cifs manager can be downloaded doesn't mean it has Cifs support.
You need a custom rom / Kernel for that.
There are two kernels out there claiming cifs support, however I cant get either one to work.
http://forum.xda-developers.com/showthread.php?t=2235085&highlight=cifs
and
http://forum.xda-developers.com/showthread.php?t=2233665&highlight=cifs
Let me know if you get one working.
Update: there is a 3rd Kernel claiming Cifs support.
http://forum.xda-developers.com/showthread.php?t=2229300&highlight=cifs
I will try it our soon.
Any updates on this? Would love to have CIFS support and TAP network driver support. I'm thinking about trying to compile my own kernel modules but I have almost zero experience with doing this...
cifs.ko loads, but no success
jaybombz said:
Any updates on this? Would love to have CIFS support and TAP network driver support. I'm thinking about trying to compile my own kernel modules but I have almost zero experience with doing this...
Click to expand...
Click to collapse
I've gotten a cifs module to load on 3.4.10 after modifying the module final version string to reflect my specific kernel (3.4.10-geb45596) but still no success. I had success doing the exact same thing on my old EVO, but CifsManager on the HTC One throws "invalid argument", and the mount command (via terminal) says "no device", although lsmod confirms that cifs is loaded.
Any advice is welcome.
I'm also stuck trying to get CIFS.
Can you flash any kernel, regardless of ROM, or does it have to match? I'm using an Android Revolution HD GPE ROM, which doesn't appear to have CIFS support ("invalid argument", cifs.ko nowhere to be found in the filesystem according to ES File Explorer, /proc/filesystems/cifs (or something like that) does not exist, etc).
Maybe I could just flash one of the above kernels and see if it works, or does it not work like that, i.e. it has to be integrated with the ROM?
the title pretty well describes it. I've also disabled knox and have set SELinux to permissive.
symptom: plug in otg cable, put on thumb drive....nothing. search in file manager - nothing.
I've messed with, er, personalized the tablet and honestly can't recall all I've done, but USB OTG once worked and now doesn't. I've played with many of the 'troubleshooter' apps from the store [all useless, IMO, because all they say is yes or no].
Kernel support is there but no devices are recognized. The .xml file is present in system/etc/permissions or whatever the correct path is.
I've tried 2 different OTG cables and two different thumbdrives.
I've tried with selinux permissive and enforcing
I've rebooted both with and without the otg usb drive attached.
where can i look? are there any troubleshooting tools that give actual information?
i'm reasonably intelligent (PhD in physics) but not all that savvy with android (which, btw, i hate ) but i was once a unix sysadmin, so i fear no cli.
device is rooted, twrp installed if i recall correctly. completely unwilling to change kernels (unless there's a stock 7.1 or 8 )
thoughts? suggestions?
<rant>
[why do i hate android? why take a Ferrari and fix it so it will only go 50 mph? this is powerful hardware and software, but we're all treated like little children with no root control, hoops to jump through to change selinux, Samsung's god-awful knox, etc. etc. And android networking needs to get out of the 80s. DOS/Novell was better. i want to share drives from my tablet, and i want to mount drives from my PC so the contents are as available as the internal memory.]
</rant>
Using N4N 1.3 kernel with stock I6, TWRP, rooted using Magisk and OTG working flawless in my T810.
Read the changes: https://forum.xda-developers.com/tab-s2/development/kernels-n4n-i6-i5-710-715-810-815-t3700601
Hi mates
I am new to rooting n stuff.
But i am impressed by the MAGISK SYSTEMLESS CONCEPT.
I would like to suggest some development pathways.
1. Can drivers and firmwares be added systemlessly?
Eg. Add support to AWUS036H/ALFA wifi adapter and enable monitor mode
2. Samsung pay : Systemless support to fake Knox Status
And so on
My device is note 9 exynos. Any suggestions? Am i thinking right or wrong?
Not really my area of knowledge, but I believe neither is possible with Magisk.
Magisk does it's thing on the /system and /vendor partitions and I think that neither of your mod examples have anything to do with those partitions. #1 likely has to be added to the kernel (or something like that) and #2 has its own protected partition (or something like that, if I remember correctly) and cannot be altered.
Hopefully someone that actually knows what they're talking about will chime in and let us know if I'm just spouting nonsense...
Delete
There is actually a set of wireless adapter firmwares available through a Magisk module but your kernel also needs support for external USB network adaptors. In order for that to be accomplished your kernel needs to be compiled with that support. Magisk works on too high of a level to add that support through a module afaik.