Related
Hey guys, as always, thanks in advance.
I've been playing with the Galaxy Tab for a week or two, and it is fantastic. I was able to easily root it by downloading z4Root, and running that. Now I have a slightly different request. Is there a way to manually get root on the device without the use of programs like z4Root or SuperOneClick?
My assumption is that these programs are running an elaborate series of commands, and it is usually just simpler for most of us to download an existing root exploit, than to do it manually. What I'm looking for, is a way to automate the entire process of rooting a device from Sprint, removing the preinstalled Bloatware, making a few settings changes, and installing a few applications. I want to do this with no need for any interaction on the Galaxy (other than turning on USB debugging and plugging it in), including running z4Root and clicking the buttons.
I'm writing a batch file to send all the adb commands necessary, as I've done on previous Android devices. Say for instance I want to install this on 50 different devices, I'd prefer to not have to run z4Root on each of them by hand. On a previous Android tablet I was able to do something like this:
Code:
adb shell mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
adb shell cat /system/bin/sh > /system/bin/su
adb shell chmod 4755 /system/bin/su
adb shell reboot
But that doesn't work on the Galaxy obviously. I'm just wondering if there is something similar. Basically, can someone explain to me how the z4Root exploit works? What exactly is going on under the hood? I suspect though, that it may require significantly more complicated logic that could/should be done in a simple batch file.
Here is what I'm looking to have when I'm done:
The Galaxy Tab will be used for an in-house, single purpose app. (Meaning, I don't need custom UI, phone calling hacks, etc).
The app I will be running does not actually need root itself to run even, meaning after I remove the bloatware and change a few settings, I don't even care if I KEEP Root access after things are set up.
I would like to avoid (if possible) adding any more programs/apps/files to the phone than necessary, meaning I'd prefer to not leave a "SuperUser" app in the menu if possible. And I want to find something that won't have a lot of licensing restrictions to my use.
I'm sorry that sounds complicated, and I tend to drone on, giving far more information than is actually needed. In short, lets just start with- "How does z4Root work?" Thanks again as always guys. I appreciate the help.
DavidThompson256 said:
In short, lets just start with- "How does z4Root work?" Thanks again as always guys. I appreciate the help.
Click to expand...
Click to collapse
In essence, it uses the "RageAgainstTheCage" exploit
You may find this tutorial that I wrote for the Toshiba AC100 useful, as I'm pretty certain most of it applies to the Tab.
Regards,
Dave
EDIT- or you can just follow this thread instead which does much the same thing, but is Tab specific!
Ah, yes, I just finished reading that thread, and it had EXACTLY what I needed! I feel kind of dumb because that other thread was posted WHILE I was in the process of typing up my post. I guess I just type slow
Anyway, I'm willing to call this one closed already. I was able to find everything I need in blacklevel's post over here.
Thanks for the help.
I have been trying to get the kindle fire software running on the Gtablet, so far I can get through registration. After that force closes like crazy. If anyone has any ideas that might help feel free to discuss, in the mean time I will keep at it and see what happens, and if I get it to a useful state I will release it. I am currently using Flashback as a base which may account for some of the issues since the kindle fire runs 2.3 however I have had less apps crash on HC.
I have added crash logs below and rather than upload all the apps/libs that are required to even boot the launcher, I have uploaded a CW rom flash for the 1.2 bootloader only!! The rom is tlbardelljr's Flashback with some amazon stuff added.
*Update* I have managed to get it past registration, but then it force closes (com.amazon.kindle.otter). I am now at a stand still until I either learn more about modding apps to work with the core os, or I find a developer who has more knowledge than I to help get this going. If you are interested in helping and are knowledgeable in this area please contact me with a PM. Thanks, and in the mean time I will get to learning
*Update 11-26-11* Thanks to rajeevvp I am getting a little bit further with sorting out errors (I get past registration now) hopefully I will have something new soon.
*Update 12-6-11* The issues appear to be OpenGL/Driver related now, so for now I am putting this project aside. If anyone would like to take over from here feel free.
Warning: This is for testing purposes only!!! Be sure you know how to use nvflash!!!
Code:
11-26 12:31:39.927: W/InputManagerService(1031): Got RemoteException sending setActive(false) notification to pid 2203 uid 10025
11-26 12:31:39.927: E/AndroidRuntime(2393): FATAL EXCEPTION: GLThread 14
11-26 12:31:39.927: E/AndroidRuntime(2393): java.lang.IllegalArgumentException: Thread: + GLThread 14 No configs match config spec
11-26 12:31:39.927: E/AndroidRuntime(2393): at com.amazon.kindle.otter.ogl.FSAAConfigChooser.chooseConfig(FSAAConfigChooser.java:102)
11-26 12:31:39.927: E/AndroidRuntime(2393): at android.opengl.GLSurfaceView$EglHelper.start(GLSurfaceView.java:981)
11-26 12:31:39.927: E/AndroidRuntime(2393): at android.opengl.GLSurfaceView$GLThread.guardedRun(GLSurfaceView.java:1326)
11-26 12:31:39.927: E/AndroidRuntime(2393): at android.opengl.GLSurfaceView$GLThread.run(GLSurfaceView.java:1180)
11-26 12:31:39.937: D/SurfaceFlinger(1031): screenshot: sw=173, sh=101, minZ=0, maxZ=21010
11-26 12:31:39.937: W/ActivityManager(1031): Force finishing activity com.amazon.kindle.otter/.Launcher
http://www.multiupload.com/HW4GXSCNF7 - Rom
http://www.multiupload.com/1HBY5YH7ST - Full Crash Log
Just out of curiosity. Since the Kindle Fire software was developed for froyo, have you tried like a vegan tab 5.11 ROM. I know some modules in the kernel software are present in the vegan froyo ROMS that are not present in the later kernels. This is a great idea and I will be watching this thread with great anticipation. Maybe you could post the software you are trying to load. Like if it is an APK host with mediafire or something. Then others like me can download and try to get it working too. once again GREAT IDEA!!!!!
Awesome, this is exactly what I want, wish I could help
Sent from my HTC Glacier using xda premium
I thought the kindle fire was gingerbread?
Sent from my GTablet using Tapatalk
I think you are right. I read an old article, it is 2.3. I will be updating with my crash logs and files soon.
Sent from my Nexus S using XDA App
barracudacm said:
Just out of curiosity. Since the Kindle Fire software was developed for froyo, have you tried like a vegan tab 5.11 ROM. I know some modules in the kernel software are present in the vegan froyo ROMS that are not present in the later kernels. This is a great idea and I will be watching this thread with great anticipation. Maybe you could post the software you are trying to load. Like if it is an APK host with mediafire or something. Then others like me can download and try to get it working too. once again GREAT IDEA!!!!!
Click to expand...
Click to collapse
I have tried vegan with no luck, the launcher won't even start on vegan. I have also tried to make a full from port with the vegan kernel and I can't get it to boot. I am not super experienced with ports though. I am a themer at heart, but just decided to try this because it is something that I would use a lot.
Sent from my Nexus S using XDA App
I am guessing they made quite a bit of changes to the underlying system
Sent from my HTC Glacier using xda premium
the3dman said:
This is the main error I am trying to figure out (com.amazon.dcp):
Click to expand...
Click to collapse
At least 3 errors are readily evident from the log file.
1. "No JNI_OnLoad found in /system/lib/libCommonWrapper.so 0x40587208, skipping init"
This looks like the wrong libCommonWrapper.so library is being used. Check for multiple copies of this file, or, if there is only one copy, try using the /system/bin/linker and /system/lib/libdl.so from the Kindle Fire.
2. "Error creating directory /system/etc/labdictionary"
The /system partition may be mounted read-only or the application trying to create the directory might not have permissions to create it in /system/etc. Create the directory and use the permissions of the original dir on the Kindle Fire.
3. "Native KRF library failed to load.
java.lang.UnsatisfiedLinkError: Couldn't load ft2KRF: findLibrary returned null"
This looks like a straightforward library missing problem. Look for any *KRF* in /system/lib on the Kindle Fire and copy those files to the same place on your ROM.
rajeevvp said:
At least 3 errors are readily evident from the log file.
1. "No JNI_OnLoad found in /system/lib/libCommonWrapper.so 0x40587208, skipping init"
This looks like the wrong libCommonWrapper.so library is being used. Check for multiple copies of this file, or, if there is only one copy, try using the /system/bin/linker and /system/lib/libdl.so from the Kindle Fire.
2. "Error creating directory /system/etc/labdictionary"
The /system partition may be mounted read-only or the application trying to create the directory might not have permissions to create it in /system/etc. Create the directory and use the permissions of the original dir on the Kindle Fire.
3. "Native KRF library failed to load.
java.lang.UnsatisfiedLinkError: Couldn't load ft2KRF: findLibrary returned null"
This looks like a straightforward library missing problem. Look for any *KRF* in /system/lib on the Kindle Fire and copy those files to the same place on your ROM.
Click to expand...
Click to collapse
Thanks for the assistance, it is much appreciated. I will definitely try these.
Sent from my Nexus S using XDA App
rajeevvp said:
At least 3 errors are readily evident from the log file.
1. "No JNI_OnLoad found in /system/lib/libCommonWrapper.so 0x40587208, skipping init"
This looks like the wrong libCommonWrapper.so library is being used. Check for multiple copies of this file, or, if there is only one copy, try using the /system/bin/linker and /system/lib/libdl.so from the Kindle Fire.
2. "Error creating directory /system/etc/labdictionary"
The /system partition may be mounted read-only or the application trying to create the directory might not have permissions to create it in /system/etc. Create the directory and use the permissions of the original dir on the Kindle Fire.
3. "Native KRF library failed to load.
java.lang.UnsatisfiedLinkError: Couldn't load ft2KRF: findLibrary returned null"
This looks like a straightforward library missing problem. Look for any *KRF* in /system/lib on the Kindle Fire and copy those files to the same place on your ROM.
Click to expand...
Click to collapse
I have set permissions and created the directory but am still getting: "Error creating directory /system/etc/labdictionary"
Also I cannot use the linker from the kindle I just get bootloops when I try.
Not quite sure if this will help. But here is a gingerbread kernel that slimm6099 compiled for me for use with gingerbread. He used alot of normally unused modules to make it,.. including loop device support and swap functionality. Just thought it might help.
http://dl.dropbox.com/u/14075340/barracudacm-kernel.zip
p.s. I cant boot linux or bactrack5 on gingerbread without this kernel. (dont know if thats relevant?!......)
barracudacm said:
Not quite sure if this will help. But here is a gingerbread kernel that slimm6099 compiled for me for use with gingerbread. He used alot of normally unused modules to make it,.. including loop device support and swap functionality. Just thought it might help.
http://dl.dropbox.com/u/14075340/barracudacm-kernel.zip
p.s. I cant boot linux or bactrack5 on gingerbread without this kernel. (dont know if thats relevant?!......)
Click to expand...
Click to collapse
Thanks, I will give it a shot.
Sent from my Nexus S using XDA App
the3dman said:
I have set permissions and created the directory but am still getting: "Error creating directory /system/etc/labdictionary"
Click to expand...
Click to collapse
Hmm. That's strange. Are other dirs/files missing? Try doing a filesystem comparison using the file listing on both devices using adb if possible. On a Linux system (on Windows, install Cygwin first):
Code:
[I]Connect gTab to PC[/I]
$ [B]adb shell find /system | sort > gtab-find.txt[/B]
$ [B]adb shell ls -lR /system > gtab-ls.txt[/B]
[I]Disconnect gTab and connect Kindle Fire[/I]
$ [B]adb shell find /system | sort > kfire-find.txt[/B]
$ [B]adb shell ls -lR /system > kfire-ls.txt[/B]
[I]Find differences[/I]
$ [B]diff -Bbu gtab-find.txt kfire-find.txt[/B]
Then look for dirs/files missing on the gTab and use the detailed listing in the kfire-ls.txt as a guide to creating the correct permissions.
Also I cannot use the linker from the kindle I just get bootloops when I try.
Click to expand...
Click to collapse
That is a risk you always take when messing around with the linker. Did you also copy the /system/lib/libdl.so library? Try using the linker and libdl.so from the latest CyanogenMod update.zip file.
rajeevvp said:
Hmm. That's strange. Are other dirs/files missing? Try doing a filesystem comparison using the file listing on both devices using adb if possible. On a Linux system (on Windows, install Cygwin first):
Code:
[I]Connect gTab to PC[/I]
$ [B]adb shell find /system | sort > gtab-find.txt[/B]
$ [B]adb shell ls -lR /system > gtab-ls.txt[/B]
[I]Disconnect gTab and connect Kindle Fire[/I]
$ [B]adb shell find /system | sort > kfire-find.txt[/B]
$ [B]adb shell ls -lR /system > kfire-ls.txt[/B]
[I]Find differences[/I]
$ [B]diff -Bbu gtab-find.txt kfire-find.txt[/B]
Then look for dirs/files missing on the gTab and use the detailed listing in the kfire-ls.txt as a guide to creating the correct permissions.
That is a risk you always take when messing around with the linker. Did you also copy the /system/lib/libdl.so library? Try using the linker and libdl.so from the latest CyanogenMod update.zip file.
Click to expand...
Click to collapse
Thanks for the help, I will attempt this when I have a free chance.
I'm really hoping to see this working on g tablet soon. I'd like to see what the kindle fire software is like.
bdds13 said:
I'm really hoping to see this working on g tablet soon. I'd like to see what the kindle fire software is like.
Click to expand...
Click to collapse
Same here, this will be really cool.
Well after playing around some more I got it narrowed down to one major issue. OpenGL seems to be what is now causing the force close, and I think until we get some proper drivers we are sol. I could be wrong, like I stated in the OP I am just an amateur at this. So for now I am going to take some time away from this, but if anyone would like to pick up from where I am leaving off then feel free.
the3dman said:
Well after playing around some more I got it narrowed down to one major issue. OpenGL seems to be what is now causing the force close, and I think until we get some proper drivers we are sol. I could be wrong, like I stated in the OP I am just an amateur at this. So for now I am going to take some time away from this, but if anyone would like to pick up from where I am leaving off then feel free.
Click to expand...
Click to collapse
I think you are right, the problem with all the ROMS for G tablet seems to be proper Nvidia drivers.
Hi All:
I'm a long time Viewsonic GTablet owner and have ran just about every ROM xda/slatedroid/ and other have to offer.
I really appreciate the work that ppl have done here but was curious as to why other than just because we can.
My friend has purchased a Kindle Fire and there are a few things really like about it and somethat I really hate. This all JMO and in no way am I trying to knock the work being done here. With that said, here are some of my observations:
-PRO- Kindle Fire UI is one of the cleaniest I have ever seen and I've been a tablet user for over a year now.
-PRO- the "newstand" UI concept is one that can get even the most non tech person into a tablet with the least amount of pain
-CON- Marketplace is not available
-CON- need to setup yet another email account on amazon (cant use a google account)
-CON- cant add additional mail accounts (gmail, yahoo, hotmail, etc) simpily
My overall impression is that the Fire is a inexpensive Ipad for digital consumer that want to do just that, consume, and not pay $700 to have the right to do so.
Good luck too all and happy holidayz, I'll keep an i-out to see if we make any progress and will glady be a alpha-beta tester.
nyciz said:
Hi All:
I'm a long time Viewsonic GTablet owner and have ran just about every ROM xda/slatedroid/ and other have to offer.
I really appreciate the work that ppl have done here but was curious as to why other than just because we can.
My friend has purchased a Kindle Fire and there are a few things really like about it and somethat I really hate. This all JMO and in no way am I trying to knock the work being done here. With that said, here are some of my observations:
-PRO- Kindle Fire UI is one of the cleaniest I have ever seen and I've been a tablet user for over a year now.
-PRO- the "newstand" UI concept is one that can get even the most non tech person into a tablet with the least amount of pain
-CON- Marketplace is not available
-CON- need to setup yet another email account on amazon (cant use a google account)
-CON- cant add additional mail accounts (gmail, yahoo, hotmail, etc) simpily
My overall impression is that the Fire is a inexpensive Ipad for digital consumer that want to do just that, consume, and not pay $700 to have the right to do so.
Good luck too all and happy holidayz, I'll keep an i-out to see if we make any progress and will glady be a alpha-beta tester.
Click to expand...
Click to collapse
I am also a kindle fire owner. When I am not making themes for my GTab, I really only use the GTab as an e-reader and to browse the net. I never use the google market on it, I use the amazon one though for the free apps, I don't check email on it I either use my nexus s or my computer. So really the only stuff I use is the amazon stuff, so I figured why not just have 2 kindle fires around the house so that when my wife is reading on the real fire, I have my own GFire to read on with a bigger screen. But I was also doing it because I love the UI and like you said because I can (It was something to keep my busy).
Hello,
I wanted to know if there's any way to "share" the apps installed on each ROM so I don't have to be installing them each time I add a new ROM. I've searched the forums and I only found this: http://forum.xda-developers.com/showthread.php?t=872742 which is quite old and things might have changed by now. I also understand that I won't be able to share *every* app as some of them are Froyo/GB/ICS/JB specific.
Thanks!
J_M_V_S said:
Hello,
I wanted to know if there's any way to "share" the apps installed on each ROM so I don't have to be installing them each time I add a new ROM. I've searched the forums and I only found this: http://forum.xda-developers.com/showthread.php?t=872742 which is quite old and things might have changed by now. I also understand that I won't be able to share *every* app as some of them are Froyo/GB/ICS/JB specific.
Thanks!
Click to expand...
Click to collapse
You mean, share apps btw the virtual systems?, or btw the real and the virtual?
LeonardoJegigzem said:
You mean, share apps btw the virtual systems?, or btw the real and the virtual?
Click to expand...
Click to collapse
Either. Ideally both but I don't mind if I can only share between RS and VSs or between VSs. Is it possible, then?
J_M_V_S said:
Hello,
I wanted to know if there's any way to "share" the apps installed on each ROM so I don't have to be installing them each time I add a new ROM. I've searched the forums and I only found this: http://forum.xda-developers.com/showthread.php?t=872742 which is quite old and things might have changed by now. I also understand that I won't be able to share *every* app as some of them are Froyo/GB/ICS/JB specific.
Thanks!
Click to expand...
Click to collapse
Real to Virtual :
You can browse /fshook/mounts/data/apps to find the apps in real system. However TB is the best way to go.
Virtual to Real :
In terminal emulator,
Code:
su
mkdir -p /data/local/mnt/data
mount -o loop -t ext3 /mnt/sdcard/multiboot/<Vfs name>/data.img /data/local/mnt/data
Then you can browse /data/local/mnt/data for apps. After completing installing,
Code:
su
umount /data/local/mnt/data
Thank you very much royale1223! I thought about TB but I wanted to know if there was any other method. I presume that if I go to /fshook/mounts/data/apps in the VS I will able to install them in the VS or will I be able to run then directly?
I'm currently running an OMNI build for everest, which is working delightfully well. The only thing I can't seem to achieve is to mount a CIFS directory. Actually, it can be mounted, but its contents are only visible to root.
While doing some research I found this thread. For what the description says, I assume this fix has been applied in CM, since I was able to mount CIFS (outside of /storage) before switching from CM to OMNI.
Would these patches be applicable for OMNI? If so, I would try to ask the everest ROM creator to apply them, or even try myself. But I'm afraid I may be lacking the knowledge to judge whether it'd just be a waste of time.
Thanks in advance for any tips on this matter.
Any update on the topic? I've tried Omni on my Nexus 10 and it runs perfectly well but this is the last thing that stops me from using the ROM. After mounting the data from my CIFS or NFS share the data is only available from the app performing the mount. The patches in the link from the previous post seems to work around this issue, is there any chance it could be applied to OmniROM?
Try to mount your folders manually (or by GScript) with Superusers --mount-master switch to make the mounts available to all processes. Something like this.
The su binary now also has a "--mount-master" option that connects you to a su session in the main mount namespace. Mount commands in this session should affect all processes. This is still a bit experimental, and getting it working requires a reboot after upgrading the binaries from a pre-1.93 version. This feature has been asked for a lot by devs, and it escapes the need to hijack system services to affect system-wide mounts, which is becoming more complicated with every Android release. A new version of StickMount will be released in a few days as well, taking advantage of this feature, and thus avoiding a number of issues some are seeing.
https://plus.google.com/+Chainfire/posts/hLKytCwUm6k
Click to expand...
Click to collapse
Alternatively, there is still the possibility to hijack a system service (like SSH one) to point to a script instead that will bring up your mounts. I'm personally using this so i haven't checked the SU method yet.
Good Luck!
DualJoe said:
Try to mount your folders manually (or by GScript) with Superusers --mount-master switch to make the mounts available to all processes. Something like this.
Alternatively, there is still the possibility to hijack a system service (like SSH one) to point to a script instead that will bring up your mounts. I'm personally using this so i haven't checked the SU method yet.
Good Luck!
Click to expand...
Click to collapse
Thanks, --mount-master works like a charm!
Hi all,
First thread here .
So, on with it. I've been a member on this forum for quite some time, but never felt like posting or anything as I didn't have anything interesting to share and all the questions I might've got at some point got already answered...
Anyway, about a year a go I bought a Samsung Galaxy S III. Cute little 'monster', powerful and all... and I got hit by MTP. I'm a Linux user, so getting MTP to work was a huge pain. So I started reading, digging, found out that some guys already implemented some scripts for mounting the external SD as UMS... the problem was that they didn't work on my end.
So I developed my own little app. Nothin' fancy, two buttons to switch from MTP to UMS and back.
In the meanwhile, I changed my phone to a Note 2 LTE and did some more tweaking on my app and now I'm kinda ready to share it with you guys:laugh:.
You need to have a rooted phone equipped with busybox (my app will prompt warnings telling you you're not rooted or you don't have busybox, but I thought it was nice to tell you here the requirements).
One small thing, besides the usual "I'm not responsible to any damages brought to your phone and all": after transferring to / from your SD card, please use the eject command (or the safety remove feature on Windows) to unbind the card from your operating system before changing back to UMS. That way you ensure no harm is brought to you SD card or to the data on it.
All that being said, you can download the app from here: devver.ro/ums-mounter/ (I don't have enough posts to give an external link, so you'll have to enter the text manually in your browser). The text on that page is written both in Romanian (my native language) and English so there shouldn't be any problems .
This app should work on every device that has an SD card and runs Android 4.3+. Oh yeah, there might be some glitches on devices with Samsung's official releases (bummer, I know), but that's related to some screw-ups on their end, 'cause they're random from ROM to ROM.
Anyway, hope you'll like it (if you test it). If you have and problems, comment here and attach a logcat and I'll see if I'm smart enough to help you.
== 2014-06-10 ==
Version 1.1
Changes:
- please uninstall the previous version, as I've changed the signature on the file ;
- added a small sanity check which will force you to unplug your phone from the computer before switching between modes (hopefully this will also force you to safely remove the external sd card );
- fixed (i hope at least) the situation where the card is not mounted as usb on Touchwizz related ROMs;
As usual, the app can be downloaded from devver.ro/ums-mounter. Thanks again for testing .
sleepwalker123 said:
This app should work on every device that has an SD card and runs Android 4.3+.
Click to expand...
Click to collapse
It mounts the card slots (although it needs a reboot sometimes), but the PC shows up two empty usb slots and the sd card is not mounted.
Im running DN3 V5+.
I do hope you can fix it.
Thank you.
@erljayp: that's one ROM which is based on a stock ROM and, as I mentioned in my OP, there might be glitches woth 'em.
I'll setup my phone into dual booting so that's gonna be a bit easier to test these ROMs and hopefully sort them out.
Thanks for testing my little app
your app said that i haven't installed busybox yet. then i tried to install busybox from play store and it said the same. what problem?
ectv96 said:
your app said that i haven't installed busybox yet. then i tried to install busybox from play store and it said the same. what problem?
Click to expand...
Click to collapse
I've used play.google.com/store/apps/details?id=stericson.busybox to install busybox. Basically, after you install the app from the play store, you need to open it in order for it to actually download and install the busybox binaries. If you just downloaded the app from play store but didn't actually open it, that may be the problem
sleepwalker123 said:
I've used play.google.com/store/apps/details?id=stericson.busybox to install busybox. Basically, after you install the app from the play store, you need to open it in order for it to actually download and install the busybox binaries. If you just downloaded the app from play store but didn't actually open it, that may be the problem
Click to expand...
Click to collapse
oh yes, it works. thankyou :good::laugh:
New version, please check OP. Should resolve the DN3 related issues (this should apply to all ROMs which are based on stock Samsung). 'Njoy!
sleepwalker123 said:
there might be glitches woth 'em.
Click to expand...
Click to collapse
I thought you were talking about the "stock" rom. haha.
sleepwalker123 said:
Should resolve the DN3 related issues.
Click to expand...
Click to collapse
Now working in DN3 V5+, but I have fluctuating transfer rates. What is the average transfer rate you have?
Thank you.
@erljayp: i get about a maximum of 2 MB/s transferring a file bigger than 50-100 MB, which I find quite satisfying. Also, if I'm not mistaking, the transfer rates are influences by a lot of factors: the card's class, if you're transferring a lot of small files (mp3's, for example) etc.
Anyway, glad that sorted your problem. Like I said before, my app should now work not only on the DN3, but on all ROMs (CM11 based, AOSP, AOKP, ROM's based on the stock Samsung release). If you find a ROM that won't work, Iemme know and I'll see what's to be done about it .
sleepwalker123 said:
@erljayp: i get about a maximum of 2 MB/s transferring a file bigger than 50-100 MB, which I find quite satisfying. Also, if I'm not mistaking, the transfer rates are influences by a lot of factors.
Click to expand...
Click to collapse
I guess mine is normal.
Well, thank you very much for this great app and goodluck in your future projects.
sleepwalker123 said:
Hi all,
First thread here .
So--------.
Click to expand...
Click to collapse
The App crashes when trying to switch the pages.
Is this working on 4.4.2 TW roms ?
aukhan said:
The App crashes when trying to switch the pages.
Is this working on 4.4.2 TW roms ?
Click to expand...
Click to collapse
Don't try and switch pages All you need to do is "play" with the 2 buttons. I think the "page" you're referring to is something i use for debugging.. will remove it in a future release
sleepwalker123 said:
Don't try and switch pages All you need to do is "play" with the 2 buttons. I think the "page" you're referring to is something i use for debugging.. will remove it in a future release
Click to expand...
Click to collapse
I use Switch UMS and connect USB is that right any requirements to run the app apart from Root and busybox ?
aukhan said:
I use Switch UMS and connect USB is that right any requirements to run the app apart from Root and busybox ?
Click to expand...
Click to collapse
Nope. Those are the only requirements. Could you please give me a link to your ROM's thread?
sleepwalker123 said:
Nope. Those are the only requirements. Could you please give me a link to your ROM's thread?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?p=36202763#post36202763
Does this support windows or only linux??
aukhan said:
http://forum.xda-developers.com/showthread.php?p=36202763#post36202763
Does this support windows or only linux??
Click to expand...
Click to collapse
Grr... can't test that one...
Could you please connect your phone to your, connect into an adb shell, run mount and give me the output? Or if you have the Terminal Emulator app installed, do it from there and gimme the output.
sleepwalker123 said:
Grr... can't test that one...
Could you please connect your phone to your, connect into an adb shell, run mount and give me the output? Or if you have the Terminal Emulator app installed, do it from there and gimme the output.
Click to expand...
Click to collapse
You want me to run this # mount in terminal emulator and give you the results ?
Should i be connected to PC or not ?
aukhan said:
You want me to run this # mount in terminal emulator and give you the results ?
Should i be connected to PC or not ?
Click to expand...
Click to collapse
You don't have to be connected to the computer. Try and run the following in the terminal emulator:
- su (if you didn't);
- mount > /sdcard/mount.log
And after that, on your internal storage you shall find a file called mount.log. Give me the contents of that file, please.
sleepwalker123 said:
You don't have to be connected to the computer. Try and run the following in the terminal emulator:
- su (if you didn't);
- mount > /sdcard/mount.log
And after that, on your internal storage you shall find a file called mount.log. Give me the contents of that file, please.
Click to expand...
Click to collapse
Usage: mount [-r] [-w] [-o options] [-t type] device directory.
aukhan said:
Usage: mount [-r] [-w] [-o options] [-t type] device directory.
Click to expand...
Click to collapse
I think you ran the command including the dash ("-" sign).
Perhaps i didn't express myself well enough, sorry...
1). su (for gaining root access, no matter if you're doing this from the terminal emulator or from your pc);
2). mount > /sdcard/mount.log
Again, sorry for the confusion.