Can anyone please explain this, and how I can apply the same?
Rom is working well Had to use a fuser script to get my ntfs card to work but that's no biggie
Having the same issue as this gent and need to apply the same fix.
Related
Hi People... It's my first post, so please be gentle!
Thanks to this board I now have a fully rooted X10i - everything went smooth except for having 64bit java, but found answers to everything here, so props to all you lot.
I've got all the usual suspects installed on a rooted phone (root explorer, set cpu, cachemate, root manager etc) - all working fine.
But... the one that interests me the most is Autostart. 3 questions:
1) I've added a busybox command to automatically mount the filesystem as rw and that works great. - Is that super dangerous to do?
2) I saw some others that have installed autostart have added a command to use swapon /sdcard - when I try that I get "unsupported" - I'm guessing that is because we don't have custom ROM yet, and the generic kernel does not support swap?
3) Can anyone suggest any other good uses of an autostart script?
Thanks peeps, and peace out...
Check this out
adamsweeting said:
Hi People... It's my first post, so please be gentle!
Thanks to this board I now have a fully rooted X10i - everything went smooth except for having 64bit java, but found answers to everything here, so props to all you lot.
I've got all the usual suspects installed on a rooted phone (root explorer, set cpu, cachemate, root manager etc) - all working fine.
But... the one that interests me the most is Autostart. 3 questions:
1) I've added a busybox command to automatically mount the filesystem as rw and that works great. - Is that super dangerous to do?
2) I saw some others that have installed autostart have added a command to use swapon /sdcard - when I try that I get "unsupported" - I'm guessing that is because we don't have custom ROM yet, and the generic kernel does not support swap?
3) Can anyone suggest any other good uses of an autostart script?
Thanks peeps, and peace out...
Click to expand...
Click to collapse
1. Mounting /system as rw automatically... hmmm... sounds useful, but is it? I don't know about dangerous, but take a look at this:
http://forum.xda-developers.com/showthread.php?t=712951
2. Don't know and didn't try. But, sounds interesting... will look into it. I was more inclined to first create an ext3 filesystem on the sdcard and move stuff around from the /data filesystem on to there...
3. Well once we get a working custom ROM, we can use groh_kun's splboot loader to boot into it.
This is extremeley far away from howto implementing ntfs read write support in rooted archos gen9 devices.
Everybodey is welcomed to bring on ideas and modifications.
my linux know how is not too much.
Somebody interested to help implement ntfs-3g rw for rooted archos gen9?
First - is it possible?
a) It could be possible with ntfs-3g from tuxera, on their website they say its for android, too.
b) When kernel side ntfs (the read only one) is set - can one use ntfs-3g with fuse instead or does it conflict?
Dont know if ntfs in kernel is set as yes or module. Can somebody confirm something?
Second - Which files are to be transported in which directory and which are to be modificated?
What mechanism (auto)mounts blockdevices (also sticks, flash cards, etc ...)
Is it archos specific or something related to android?
Does somebody know which daemon does this job especially on g9 and what config files it has?
Is it /etc/fstab (only) ?
Downloaded the source code from ntfs-3g and have to look.
attached ntfs-3g latest stable release as source from Tuxeras Website.
had a look in running kernel modules with
adb shell lsmod
Fuse is loaded as kernel module and active.
Therefore, i assume, one could push an arm version of ntfs-3g and ntfsprogs in the directorys in a dirty way and edit some fstab entrys or other config files?
Apropos arm version. Is there somebody who was able to (cross)compile ntfs-3g for arm and attach neccessary files?
NTFS read fine on my kingston 16 GB flash.
Write on flash dont work. How fix dont know, but i'll try to search info =)
Yes, ntfs CAN be read, but we need Write-Support.
On linux no problem, and Android IS Linux. On Arm instead of x86 or a64
Everey x86-linux has Write Support.
Thanks.
gegabit said:
NTFS read fine on my kingston 16 GB flash.
Write on flash dont work. How fix dont know, but i'll try to search info =)
Click to expand...
Click to collapse
However, thank you for your report
Found It
Hi svennimann
I was going to take up this challenge and have a go at compiling it, however this post In the galaxy S2 forum has it covered.
You don't need the worry about the fuse.ko as the archos kernel already has it and It wouldn't have the right magic anyway.
I'll probably have a poke around with integrating it more into the kernel, get it to use ntfs-3g by default.
I'll post an update, if I find anything interesting out.
Wow!
Hadnt found it but who searches on galaxy thread for archos things?
And That should be on general android thread.
We are lucky now.
Okay.
Now it is possible that there are issues with mount points, scripts, and so on, and perhaps one had to change ntfs-3g permissions to 755.
for the case that something doesnt work, i think this could be do the trick if neccesary.
http://forum.xda-developers.com/showpost.php?p=15490573&postcount=49
Apropos what do you mean with right magic of the fuse module?
Yes maybe. I only did a quick root shell test to make sure it mounted and wrote. I'll play around more with it later when I get in.
With regards to magic:
.ko files are compiled against a specific version of the kernel. They contain a vermagicapp string which is checked against the installed kernel when insmod is run. If they don't match the Kernel module won't install.
That's how I understand it.
Sent from my HTC Sensation XE with Beats Audio using xda premium
So I think I've correctly enabled init.d support on my phone... I've added a few scripts that I pulled from another ROM, but I don't know how to verify whether or not they are working correctly. Does anybody know of a quick and easy way to test whether init.d scripts are loading? Is there a test script I can insert and run that will make it obvious if it works, but doesn't do anything destructive... just to test?
OK, so I want to create a script that will set a new background image on boot to test this. that way, if init.d is working, I know because I reboot and get a different bg than the one I was just on... is that possible?
To test if it's working, drop a line like this in your script.
echo "It's working" > /sdcard/initd.log
I've read through the threads in the dev section about running linux on our Atrix either off of the sd card or chroot but didn't get a clear picture of what is possible with this technique using our phones on the laptop dock.
I'm about to give this one a go where it walks you through installing Ubuntu on our phones.
how-to-install-ubuntu-on-android
Does it work well? Does the touchpad and keyboard work without issues? Do the usb ports function correctly? And finally, does it play nice with Webtop if you have Webtop installed and enabled?
Thanks in advance for any info.
Update: The install script for this method failed when ran. It appears it is looking for a specific kernel version. The error I received was "FATAL: Could not load /lib/modules/2.6.32.9/modules.dep: No such file or directory". When I looked in the /lib/modules directory on the phone I only found a 2.6.29-arm2 directory.
you can just use WebTopScripts and Webtop2SD.
You can see how it works on my video [Polish language on video only]
http://www.youtube.com/watch?v=MGfZe4jOdfo
ovitz said:
you can just use WebTopScripts and Webtop2SD.
You can see how it works on my video [Polish language on video only]
http://www.youtube.com/watch?v=MGfZe4jOdfo
Click to expand...
Click to collapse
I checked out your video and I wish I could understand Polish.
Anyway, I just installed webtop2sd and when I launch it I get a force close error popup saying...
"Sorry! The application webtop2sd (process net.toreishi.webtop2sd) has stopped unexpectedly. Please try again."
I'm running stock 4.5.141 build with root and unlocked bootloader. Any idea on why I'm getting this error?
I can translate this video if you want to
yes, you have to instal bussybox installer form Google Play Store, then you need to change permissions of busybox in/system/bin/
Open permissions and uncheck "Set GID" permission, save changes.
ovitz said:
I can translate this video if you want to
yes, you have to instal bussybox installer form Google Play Store, then you need to change permissions of busybox in/system/bin/
Open permissions and uncheck "Set GID" permission, save changes.
Click to expand...
Click to collapse
Thanks for reminding me about Busybox. I didn't bother to install it since when I updated my Superuser binary it said it was installing a custom Busybox so I thought that would be all I would need. I guess I was wrong and had to install Busybox anyway.
I'm running the WebTopScripts at the moment. It seems to be going well.
Thanks for your help.
help please
Ok first off let me say that I am very new to android so I am a noob. Lately I have received my Atrix 4G lapdock and I have been scouring over these forums attempting to install ubuntu or some other desktop linux distro on my device for the past week.
I have installed Webtop2sd 1.1.2 (I was getting force close with 2.0 version so I downgraded :/ ) I want to partition my sdcard but it is not being recognized by webtop2sd. I have changed permissions to uncheck set GID in busybox which is installed in systym\bin ...\xbin. Still no recognition.
I have attempted to ext3 partition my sdcard with Windows Mini Tool Partition Wizard but I get and error during processing and the partition cannot be created. Currently sdcard is fat32 format.
Can anyone please provide some assistance in this it would be most helpful!
Thank you!
Device stats:
unlocked BL, rooted, and ROM Nottachtrix 4G and faux 1.3 Ghz Kernal installed
Fixed!!!
For some reason the partition tool was acting up so I used another software which did the trick.
Hello everyone, well im not sure why there isnt any support for this phone besides rooting, and im sure a lot of you already know that the Link2sd app not only doesnt work for this device but in fact it bricks it.
I have been trying to resolve this issue with no luck so far... but i have found one interesting place http://sourceforge.net/projects/i1x.motorola/files/i1x/
IN there there are the files to maybe compile a working rom? or try to push the original files to the phone in order to resolve the problem.
Does any of you knows the actual ADB procedure or any other way of doing this?.. also which file should i push to restore what the Link2sd script changed in the first place.?
I hope someone can help out..
thanks..