Related
Here's the thing.
I came from another device, and bought Nexus this week.
It's perfect for me,
except one thing which keeps me crazy.
Galaxy Nexus doesn't have SDCard.
It is only nand internal memory, and yes I can live with that just fine since it is big enough.
The problem is, there's no way to mount that internal partition into pc via usb mass storage.
I don't know what it called, but certainly it is not usb mass storage.
Yes I can see my data, copy, paste to it, but it's waaaaaay to slow.. max is only approximately 5 MBps.
And the things got more serious when transfering many many many SMALL files, like photos, or some imagery cache tiles into Galaxy Nexus via usb.
it seems it tooks forever to complete
i tried many computers, many port, many usb cable, the results remain the same.
(i tried it both on ICS stock and JB stock)
(and mount sdcard on both CWM / TWRP does not work too..)
Okay, i decided i can live with that, since no usb mass storage is good thing though.. no need to worry about unplug without safely remove.
BUT the things make me crazy is:
why the heck my photos and pictures date modified is changed into today's date?
it looks bad on gallery, the date arrangements is all wrong because of that.
i tried it by many method, including i make some flashable zip contains my photos and pictures to be flashed into:
/data/media/
(which is the real location of virtual sdcard)
but the date modified still changed, but this time it gets funnier, it says modified on 2008.
is there any way to store photos and pictures from another device into galaxy nexus but keeps the date modified stay intact?
ps:
i tried transfer files via wifi (ftp apps) too.. same results..
Sent from Galaxy Nexus - Android Jelly Bean 4.1.1
Try adb push. It will solve your problem.
Sent from my Touchpad
honest1212 said:
Try adb push. It will solve your problem.
Sent from my Touchpad
Click to expand...
Click to collapse
please, what adb command?
i tried adb push xyz /data/media/xyz/
but there's permission issue..
why?
Sent from Galaxy Nexus - Android Jelly Bean 4.1.1
marhensa said:
please, what adb command?
i tried adb push xyz /data/media/xyz/
but there's permission issue..
why?
Sent from Galaxy Nexus - Android Jelly Bean 4.1.1
Click to expand...
Click to collapse
adb push photo.jpg /sdcard/
Sent from my Galaxy Nexus using Tapatalk 2
Try Local Sync, available on play store, it works for me.
buzzcomp said:
Try Local Sync, available on play store, it works for me.
Click to expand...
Click to collapse
buzzcomp...
thank you very much for recommending it.
i already thanks all your post (it's 20 already)
anyway, you are such good man with knowledge according to all your posts..
LocalSync is the best..!!!
never thought to using it at the first place..
from now on,
i'll use it regulary.
and most importantly, it keeps date modified intact
no date modified changed... :good:
here's what i test, when syncing using Local Sync:
DELETE SCENARIO:
---------
> delete file on phone
> on pc gets deleted too..
> delete file on pc
> on phone gets deleted too..
ADD NEW FILE SCENARIO
---------
> add new file on phone
> on pc file added too..
> add new file on pc
> on phone it's added too.
EDITING / FILE CHANGES SCENARIO
---------
> edit some file on pc..
> it will updated on phone too.
> edit some file on phone
> it will updated on pc too..
EDITING / FILE CHANGES (BUT BOTH EDITED) SCENARIO
---------
> when edit some files, both edited, pc and phone
> the replaced one, is according to the settings (choose pc or phone)
MOVED FILE SCENARIO
---------
> when moving some files into new location (on phone)
> on pc the files will be moved too. it's moved, not doubled on two location.
vice versa.
UNIQUE SCENARIO
---------
> on phone, the file moved into new location.
BUT on pc that file is copied into new location (not moved, so there's two files, original location, and new location),
and the file on new location, pc, has been edited.
> the sync result is, it moved into new location, but there's two files, one is edited, one is the original (renamed into yyyyyy.orig.xxx)
Glad to hear that ..
honest1212 said:
Try adb push. It will solve your problem.
Sent from my Touchpad
Click to expand...
Click to collapse
For me, adb pull & push do not preserve original date and timestamps. However, I find this only an issue for pictures since stock gallery uses this metadata for sorting. Quickpic (available in play store) can fix this by using exif metadata to restore original file date and timestamps.
Sent from my Galaxy Nexus using Tapatalk 2
Petrovski80 said:
For me, adb pull & push do not preserve original date and timestamps. However, I find this only an issue for pictures since stock gallery uses this metadata for sorting. Quickpic (available in play store) can fix this by using exif metadata to restore original file date and timestamps.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
I realize this post is old so sorry for the bump, but: can Quickpic actually restore and write back the original timestamps? How does this work if so? I'm trying to transfer pictures with the original timestamp for days, see original thread, but so far nothing worked for me.
Mahnn said:
I realize this post is old so sorry for the bump, but: can Quickpic actually restore and write back the original timestamps? How does this work if so? I'm trying to transfer pictures with the original timestamp for days, see original thread, but so far nothing worked for me.
Click to expand...
Click to collapse
Yes it can, as long as the pictures have exif metadata.
Sent from my Galaxy Nexus using Tapatalk 2
Use Local Sync
Personally I do not understand why such a simple thing is so difficult with android tablet or phone: keep your files up to date between PC or server and the device. This is so simple with a USB stick or even with exernal drives, even with VPN. Why is this so difficult and painfull with android devices????
I (want) to use our android tablets in meetings or even in the field. So I need a sync tool to keep files up to date on the android device side (PC and/or fileserver is always master).
Android devices = Samsung Galaxy Note 10.1 (GT-N8000) with ICS 4.04 and Samsung Galaxy SIII (with GT-I9300) ICS 4.04.
I have installed Local Sync (from psencik.cz). I can connect the tablet and pairing with the PC. First remark : I notice that the android device (samsung note 10.1 tablet with ICS 4.0) never shows "USB connection" but only "MTP connection". There is simply no USB option available under "wireless and networks > more settings", so it is not possible to cancel MTP.
remark 2: the tablet shows up in Windows Explorer as GT-N8000 and files are accessible (copy, move and delete possible).
So Local Sync is installed but it is no possible to sync files from PC to Android device. About the "directory" settings to set up in the PC and the android device, nothing is clear. When I set the same directory name on both, the directory with all contents on the android device side is simply deleted !
I have seen that you are using "scenarios". How can I set these in Local Sync? is there a specific ini file to be made for this?
Please, help will be greatly appreciated.
Pierre
Pierke01 said:
Personally I do not understand why such a simple thing is so difficult with android tablet or phone: keep your files up to date between PC or server and the device. This is so simple with a USB stick or even with exernal drives, even with VPN. Why is this so difficult and painfull with android devices????
I (want) to use our android tablets in meetings or even in the field. So I need a sync tool to keep files up to date on the android device side (PC and/or fileserver is always master).
Android devices = Samsung Galaxy Note 10.1 (GT-N8000) with ICS 4.04 and Samsung Galaxy SIII (with GT-I9300) ICS 4.04.
I have installed Local Sync (from psencik.cz). I can connect the tablet and pairing with the PC. First remark : I notice that the android device (samsung note 10.1 tablet with ICS 4.0) never shows "USB connection" but only "MTP connection". There is simply no USB option available under "wireless and networks > more settings", so it is not possible to cancel MTP.
remark 2: the tablet shows up in Windows Explorer as GT-N8000 and files are accessible (copy, move and delete possible).
So Local Sync is installed but it is no possible to sync files from PC to Android device. About the "directory" settings to set up in the PC and the android device, nothing is clear. When I set the same directory name on both, the directory with all contents on the android device side is simply deleted !
I have seen that you are using "scenarios". How can I set these in Local Sync? is there a specific ini file to be made for this?
Please, help will be greatly appreciated.
Pierre
Click to expand...
Click to collapse
I dont even understand that tool. It looks so specific. Is there any FILE MANAGER with timestamp fix?
Omg back to roots.. Years after mass storage was happily introduced, it is dismissed by google plus the timestamps are forced by google. So no way to copy files. Thanks for wasting my time.
doggydog2 said:
I dont even understand that tool. It looks so specific. Is there any FILE MANAGER with timestamp fix?
Omg back to roots.. Years after mass storage was happily introduced, it is dismissed by google plus the timestamps are forced by google. So no way to copy files. Thanks for wasting my time.
Click to expand...
Click to collapse
yea we all know MTP sucks.
people loves usb mass storage.
it's just dumb, why can't we preserve date modified?
although it can be preserve by some sort of software, like localsync mentioned already, but the end-user thinks it way too advanced for them.
I don't know who started this stupid MTP things, not sure if another device without sdcard using this MTP too or not (iPhone).
it seems it has been a long time since I tried localsync, I should create tutorial for it for today's android version.
-----
Sent from Android device
And I have a phone without SD card reader, which adds up to the chaos. I already wasted hours on this. After years of efforts to add mass storage to all relevant devices by manufacturers, the Android phone became my only device without this feature.
I finally do this:
1) copy files to SD card.
2) use USB SD microreader to connect to phone via USB OTG (this technology was not yet dismissed by google)
3) install busybox on a rooted system (because google thinks COPY command is so ridiculous to keep by default, while REMOVE and MOVE is ok)
4) cp -a /Removable/USBdisk1 /sdcard
It is even very fast but not visible. I have to keep the screen on all the time otherwise USB gets disconnected (another genius designed this).
If google wants to be similar to microsoft in treating people, they can end up having similar market share in the end..
doggydog2 said:
And I have a phone without SD card reader, which adds up to the chaos. I already wasted hours on this. After years of efforts to add mass storage to all relevant devices by manufacturers, the Android phone became my only device without this feature.
I finally do this:
1) copy files to SD card.
2) use USB SD microreader to connect to phone via USB OTG (this technology was not yet dismissed by google)
3) install busybox on a rooted system (because google thinks COPY command is so ridiculous to keep by default, while REMOVE and MOVE is ok)
4) cp -a /Removable/USBdisk1 /sdcard
It is even very fast but not visible. I have to keep the screen on all the time otherwise USB gets disconnected (another genius designed this).
If google wants to be similar to microsoft in treating people, they can end up having similar market share in the end..
Click to expand...
Click to collapse
step 4, where do you type that command?
is it on terminal emulator?
yes usb otg speed is quite fast (also fast-draining battery too),
i tried copying it with solid explorer, but the date modified still changed.
maybe i should try it by terminal command like you suggest.
---
Sent from Android Device
marhensa said:
maybe i should try it by terminal command like you suggest.
Click to expand...
Click to collapse
yep.. not user friendly, especially when organizing more folders, but preserving timestamps is critical. after 20years of same file operation on dos, unix, windows, os2 etc, google wants to change the game. what what whaaat.
doggydog2 said:
yep.. not user friendly, especially when organizing more folders, but preserving timestamps is critical. after 20years of same file operation on dos, unix, windows, os2 etc, google wants to change the game. what what whaaat.
Click to expand...
Click to collapse
found the (so-called) solution...
--- PRESERVING DATE MODIFIED ON NEXUS DEVICE ---
From Android to PC: Use MTP
From PC to Android: Use Droid Explorer
cheers..
Successfully moved all my GNex photos to my N5 and preseve file created/modified date
I'm not going to lie, this was painful - but I think I've worked out the kinks.
Required:
- Source Device
> USB OTG Capable
- Destination Device
> USB OTG Capable
> Rooted
- PC (Win7x64 for me)
> ExifTool
> Bulk File Changer
- USB Stick
- OTG Cable/Connector
Steps:
1) Copy media (jpgs, 3gps, mp4s) from source device to USB stick via OTG. This could take a while depending on how much media you're copying. Don't worry about preserving the created/modified date here as you'll be fixing it on the PC using the embedded EXIF data.
1.5) While the above is happening, place ExifTool and Bulk File Changer in the following folder on your PC C:\filecreatedatefix
2) Cut and Paste the media from the USB stick over to the following folder on your PC C:\filecreatedatefix\files
3) Run the following 3 commands (one at a time) to change the created date and modified date stamps on the files to the created date in the embedded EXIF data.
C:\filecreatedatefix\exiftool "-FileCreateDate<CreateDate" "-FileModifyDate<CreateDate" -ext .jpg -r C:\filecreatedatefix\files
C:\filecreatedatefix\exiftool "-FileCreateDate<CreateDate" "-FileModifyDate<CreateDate" -ext .3gp -r C:\filecreatedatefix\files
C:\filecreatedatefix\exiftool "-FileCreateDate<CreateDate" "-FileModifyDate<CreateDate" -ext .mp4 -r C:\filecreatedatefix\files
3.5) Any files that still aren't fixed need to be done so manually using Bulk File Changer
4) Cut and Paste the media back to the USB stick in a folder like D:\Camera
5) Plug the USB stick via OTG Cable into the Destination Device and then open a terminal window
6) Type "su" (no quotes) to enter root user mode
7) Archive copy the files from the USB stick over to the destination directory using a command like the following
cp -a /sdcard/usbStorage/sda1/Camera/* /sdcard/DCIM/Camera
This could take a while depending on how much media you're copying.
8) You're done! You may need to restart the destination device in case plugging/unplugging a USB stick destabilizes it.
Petrovski80 said:
For me, adb pull & push do not preserve original date and timestamps. However, I find this only an issue for pictures since stock gallery uses this metadata for sorting. Quickpic (available in play store) can fix this by using exif metadata to restore original file date and timestamps.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Thank you thank you.
I've been looking for something like this for a long time. It doesn't work on everything, like videos and files without without the EXIF data.
But this is definitely nice to have.
omg, strugled throug that issue on my way from my nexus 5 to my OnePlus One...
Did it that way:
1. Copied all Images to my Mac
2. Sorted all Files by modified date (oldest first) with automator (see attachment)
3. Copied the output (list of files with full path in order of modification) into a TXT-File
4. Used a small perl script to push each file by "adb push" to my phone.
5. Now the order is okay, of course the modification date is gone again but because the oldest file was pushed fist it's still the oldest, even when only by seconds.
Here is my Script:
------------------------------------------------------------------------------------------
use strict;
use warnings;
my $filename = 'files.txt'; #change files.txt to your txt-file
open(my $fh, '<:encoding(UTF-8)', $filename)
or die "Could not open file '$filename' $!";
while (my $orig = <$fh>) {
chomp $orig;
my $phone = $orig;
$phone =~ s/\/Volumes\/HDD OSX\/TEST/\/storage\/sdcard0/g; # here you build the path on your phone from the path on your computer
system("./adb push \'$orig\' \'$phone\'");
}
[/script]
------------------------------------------------------------------------------------------
Initially I thought this was a problem with Google Play / Apollo, but I realize now that when I plug in my phone via USB, I can't see any of the many, many folders and files present on /sdcard that I could see previously.
If I copy a "new" mp3 onto my Galaxy Nexus, it's recognized just fine by both Google Play and Apollo. However, none of my old mp3s (or files, for that matter) are recognized. They were placed in /sdcard/Music, a folder that I cannot see when I plug in my phone, only from the file manager running on the phone. The issue persists if I move an "old" mp3 from my music folder out into the sdcard root, it's still not recognized. This makes me think this might be permission related, but the file manager says that all files are readable and writable.
I've tried running "fix permissions" in both ROM manager and the CWM recovery, but it makes no difference. Any idea what has happened, and how to fix it so that I can use all my old files again?
edit If it's any help, I just ran ls -al in a terminal emulator and I can't see any difference at all between folders I can and cannot see. Example: I can see /sdcard/media just fine, because I created that folder from Explorer in Windows. Music in that directory works. I cannot see /sdcard/music. Here's the permissions:
Code:
drwxrwxr-x root sdcard_rw 2012-09-18 media
drwxrwxr-x root sdcard_rw 2012-09-16 music
This is a bit confusing.
When I try pulling and pushing a file with adb like so:
Code:
adb pull file.tar
adb push file.tar file2.tar
I get
Code:
failed to copy 'file.tar' to 'file2.tar': Read-only file system
I've tried remounting /sdcard in root terminals both on the phone and via adb, but I get mount: Operation not permitted. I'm thinking this might be because /sdcard isn't the actual path but I've tried /storage/sdcard0 and /mnt/sdcard as well and I get the same error.
Thanks in advance for any suggestions.
(This question was also posted on android.stackexchange)
adb push /sdcard/file2.tar
also, cm doesnt have root access enabled by default for adb.
/sdcard/ is already rw, otherwise apps couldnt place anything there. nor could we.
Sent from my i9250
Didn't realize I needed an absolute path, thanks! I now managed to push the file, but it does not show up under the "Galaxy Nexus" unit in My Computer. It does show up when I do an ls in adb shell though. Any ideas?
bajsmumsaren said:
Didn't realize I needed an absolute path, thanks! I now managed to push the file, but it does not show up under the "Galaxy Nexus" unit in My Computer. It does show up when I do an ls in adb shell though. Any ideas?
Click to expand...
Click to collapse
try disabling mtp on the device; or rebooting, if you want to stick with mtp. maybe it has to refresh file list?
bk201doesntexist said:
try disabling mtp on the device; or rebooting, if you want to stick with mtp. maybe it has to refresh file list?
Click to expand...
Click to collapse
Switching from MTP to PTP does nothing, the same files are shown ("new" files). I'd like to stress that if I take a picture for example, that pictures does show up both with MTP and PTP. New files work fine. It's the old files that I can see in the file explorer in the actual phone that just refuse to show up when I connect to my computer, and they are obviously also not recognized by apps in the phone (such as Apollo or Google Play).
I realize that I could work around this issue by just removing everything from my sd card and then putting it back, but I really want to figure out how this can even happen.
I'm no expert by far, but it sounds like when you changed ROM the"index"file for mtp isn't updates. Have you tried to run the media scanner?
Swype'ed on my CM10 Galaxy Nexus
Herman76 said:
I'm no expert by far, but it sounds like when you changed ROM the"index"file for mtp isn't updates. Have you tried to run the media scanner?
Click to expand...
Click to collapse
If I've understood correctly, power cycling the device should trigger the media scanner. I just tried restarting, and it made no difference. (I've restarted the device several times since this problem occurred).
Opening the Gallery app still only shows me two pictures (I've taken two photos since the ROM flash), interestingly the thumbs are for other pictures lying around and after a while Gallery crashes. I use QuickPic more often though and that app behaves well, and shows all photos.
edit As a final resort, I tried doing a full wipe and reinstalling CM10 M1 completely, without restoring any settings or apps from any old installations. The issue still persists! Any files created with my now "old" CM10 installation no longer appear, even when they are moved within a folder where other "new" files are shown and working. This is starting to annoy me, but since this obviously is a bug in CM10 M1 I see no point in trying to spend time solving it, I'm just going to switch back to AOKP. Thank you for any answers and attempts at solving this.
edit2 Formatting /sdcard in CWM recovery fixed this, even though it might not be the most elegant solution.
Have you seen this?http://forum.xda-developers.com/showthread.php?p=30288268
Basically what it suggests is that you go to apps via settings, find the "Media Storage" app (it's a system app) Clear data/cache, then reboot. This was my problem.
Sent from my Galaxy Nexus using xda premium
This is a graphical, interactive rooting system with the ability to create/restore backups and factory settings.
This has been tested on systems 1.1.5, 1.2.0 (US/UK), and 1.2.1. It will probably work on earlier versions and should be safe to use on future versions. For best results, however, you should be on 1.2.1 before using this tool.
If you've tried rooting your nook unsuccessfully with another utility, it's best to do a factory restore (from NookManager, choose the "Rescue" option and then "Restore factory.zip") and, if your nook came with older firmware, upgrade to the latest 1.2.1 firmware.
Features:
Root your Nook
Backup/Restore
Restore to factory settings
Disable B&N Apps
Custom plugins
How to root:
1. Download NookManager.
2. Unzip the file you downloaded and write the NookManager.img file to an empty SD card. On Windows, you can use disk imager. Linux and mac users can use dd.
Use a real SD card adapter when writing the image, DO NOT USE YOUR NOOK AS THE SDCARD ADAPTER.
If possible, you should use a dedicated SD card for the NookManager image (so you can easily restore from a backup should you ever screw up your Nook). A 512Mb card is big enough for the NookManager image plus a backup of your Nook.
3. Power off your Nook, insert the SD card and power on.
You should see the NookManager boot screen followed within 15 seconds by the welcome screen.
4. Choose "No, continue without wireless"
the wireless option is for advanced users looking to connect directly to their device
5. Make a backup using NookManager! Choose "Rescue" then "Backup" then "Format remaining space on SD card" and finally "Create backup"
Because NookManager cleans the empty space on the Nooks' internal partitions and compresses the backup, it will take at least 15 minutes (and up to 45 minutes) for the backup to complete. Be patient. The final backup file can be as small as only be a few hundred megabytes, depending on the number of downloaded or sideloaded books you have.
6. Copy the backup image to your computer. Connect your Nook to your computer using the USB cable. Copy the 'backup.full.tgz' and 'backup.full.md5' files from the NookBackup drive to your computer.
This is your backup in case anything happens to your SD card. This backup is tied to your individual Nook so keep it safe. It's important to copy this file while your Nook is still booted from the SD card because Windows will normally hide the NookBackup partition on the SD card. If you ever need access to the NookBackup partition again, just boot your Nook using the NookManager SD card and connect the Nook to your computer with the USB cable.
7. Root! After your backup, press "Back" and "Back" to return to the Main Menu. Press "Root" and then "Root my device"
8. That's it! After rooting, pres "Back" and then "Exit". Remove the SD card and put it someplace safe, in case you need to restore to your backup later.
After rooting, you can install Google Apps using straygecko's excellent NTGAppsAttack package if you want to use Google Market/Gmail/Calendar/etc.
[/LIST]
Technical stuff:
The actual rooting function is minimal and as non-invasive as possible:
uRamdisk is patched to enable ADB
the internal database setting is changed to allow installation of non-market apps
the DroidSansFallback font is replaced with the updated font from jellybean to add support for extended characters
the su/Superuser binary/package is installed
Relaunch is installed
ADB Konnect is installed for enabling/disabling ADB over wireless
on systems running firmware 1.2+, the ModManager jars and package are installed
on 1.2+ systems, the PackageInstaller.apk from the 1.1.2 firmware is installed to resolve issues with package installers
and, finally, the Amazon appstore is installed just to have some easy way of downloading new apps. You can uninstall it using ReLaunch if you don't use it.
The uRamdisk patching is done with scripts rather than copying pre-compiled binaries, so this should be safe for all existing versions of the Nook firmware and (hopefully) will be forward compatible with any new releases.
The rooting procedure is non-destructive and can be run multiple times without causing problems.
Under the hood, this is a minimal linux environment with the nook drivers/binaries and a few core android binaries. The display is generated with imagemagick and written directly to the framebuffer.
If you're connecting to NookManager wirelessly over SSH, the username/password is root/root
Wherever possible, the parts of this system are compiled from source including the Linux kernel, uBoot, and all of the buildroot utilities. The hardware drivers and associated binaries are extracted from the 1.2.0 upgrade package.
The source for the project, including an automated buildscript is available at GitHub.
Support for custom menu items and scripts is documented here.
https://github.com/doozan/NookManager/downloads
NookManager.zip
17.9MB · Uploaded 14 hours ago
File was not found.
Click to expand...
Click to collapse
??
Weird. I deleted/re-upped the file and the download link seems to be working now.
ok..now it works. Thanks
Will this work with NoRefresh?
Thanks for the work on this - it was easy and worked great. And if you're planning to update, maybe add ES File Explorer or Titanium Backup in the pre-installed apps; that would make it easier to install apks directly from your SD card instead of having to do it over wireless adb. But thanks regardless.
Can confirm no refresh works great. Installed FBReader, Opera Mobile, ES File Explorer and Kindle app. Great
I just came from a firmware that had the ability to change the hardware buttons for page turning, any chance of this being added?
Thanks for this! Giving it a try.
Just curious though... I'm trying to create the backup of the device and it seems to take forever to format the free space. It also took forever to find the wireless network and I eventually just rebooted it. How long does it usually take?
I'm using a NST on 1.2.0 and have tried a 2GB Sandisk and a 8GB Dane-elec microsd card.
Gonna try redownloading and re-installing the image.
Install apk
Hi, i successfully root my NGL(1.2.0) but, if i try to install apk (Cool Reader) i got an error window "Out of space" and i'm almost sure it must be enough space to install, may someone can help with this ?
mobamoba said:
maybe add ES File Explorer or Titanium Backup in the pre-installed apps
Click to expand...
Click to collapse
Good suggestion, I've added ES File Explorer
Gvr4-330 said:
it seems to take forever to format the free space..and wifi
Click to expand...
Click to collapse
Thanks for reporting this. There was a glitch with the script that formats the SD card and with the wifi loading. Both issues have been fixed in the latest release.
asprin said:
if i try to install apk (Cool Reader) i got an error window "Out of space"
Click to expand...
Click to collapse
How are you trying to install the apk? I'm also using Cool Reader it installed with "adb install" and runs just fine. For best Nook compatibility, use coolreader 3.1.2-27 (12/11/2012 build) or later.
Originally Posted by asprin
if i try to install apk (Cool Reader) i got an error window "Out of space"
Click to expand...
Click to collapse
You get this error when you try to install application from an .apk file on sdcard or when you try to update application via it's built in updater.
ADB install works fine.
Good suggestion, I've added ES File Explorer
Click to expand...
Click to collapse
I use
Rhythm Software - File Manager
http://rhmsoft.com/?p=96
osowiecki said:
You get this error when you try to install application from an .apk file on sdcard or when you try to update
Click to expand...
Click to collapse
I'm not able to replicate this: I can copy coolreader to my sd card, and install it from there with no problems using ES File Explorer or ReLaunch. Maybe you really do have a disk space issue. Try openinng an adb shell and run "df -h" to see disk usage on your mounted partitions.
mobamoba said:
maybe add ES File Explorer
Click to expand...
Click to collapse
osowiecki said:
I use Rhythm Software - File Manager
Click to expand...
Click to collapse
It turns out you can install apks using the file browser in ReLaunch, so I'll be removing ES File Explorer in any future versions.
jeff_kz said:
I'm not able to replicate this: I can copy coolreader to my sd card, and install it from there with no problems using ES File Explorer or ReLaunch. Maybe you really do have a disk space issue. Try openinng an adb shell and run "df -h" to see disk usage on your mounted partitions.
It turns out you can install apks using the file browser in ReLaunch, so I'll be removing ES File Explorer in any future versions.
Click to expand...
Click to collapse
Thx for respond, mate, I tried install with file browser in ReLaunch from sd card, and i cant imagine that can be space issue cause i just start procedure after factory reset and rooting, anyway, thanks for tip, will try tomorrow install new build, and adb install. In general great work you did :good:
jeff_kz said:
I'm not able to replicate this: I can copy coolreader to my sd card, and install it from there with no problems using ES File Explorer or ReLaunch. Maybe you really do have a disk space issue. Try openinng an adb shell and run "df -h" to see disk usage on your mounted partitions.
It turns out you can install apks using the file browser in ReLaunch, so I'll be removing ES File Explorer in any future versions.
Click to expand...
Click to collapse
df :
/dev: 116452K total, 0K used, 116452K available (block size 4096)
/sqlite_stmt_journals: 4096K total, 0K used, 4096K available (block size 4096)
/rom: 16116K total, 227K used, 15888K available (block size 512)
/system: 285583K total, 210922K used, 74661K available (block size 1024)
/data: 824424K total, 304344K used, 520080K available (block size 4096)
/cache: 237987K total, 4179K used, 233808K available (block size 1024)
/media: 245484K total, 40K used, 245444K available (block size 4096)
/sdcard: 31149680K total, 6924320K used, 24225360K available (block size 16384)
Are you using UK or US Nook?
I'm on US Nook FW 1.2 + v176 kernel
I'm able to reproduce the apk install problems now. The "Not enough free space" error is what android throws when the internal PackageManager can't create the temporary apk file. In this case, it turns out that it's a permissions-related read error from the sdcard. I don't know if this is a matter of the internal PackageManager not running with elevated permissions, or if it's that the sdcard is mounted too restrictively.
If I re-mount the sdcard without the restrictive permissions, I can install apks from the sdcard without any errors:
Code:
umount /sdcard
mount -t vfat /dev/block//vold/179:17 /sdcard
If anyone else has any ideas for making this work, I'm open to any suggestions. In the meantime, "adb install" works just fine for installing packages.
I really suggest grabbing Android Commander if you're new to adb to graphically install apps.
jeff_kz said:
Thanks for reporting this. There was a glitch with the script that formats the SD card and with the wifi loading. Both issues have been fixed in the latest release.
Click to expand...
Click to collapse
Thanks for the quick update. I'm going to try it out now and will report back. I'm very excited
It works! Thanks so much for this! Very easy way to root and backup.
With your tool now I use this to read comics, RSS and books. First I need to say thank you.
I installed "D7 Google Reader" and "Google Drive" which requires Google Login. How could I use this software? Thanks
Also I installed version 0.2, I saw 0.3 comes out. Can I just update 0.2 to 0.3 directly? Thanks
so glad I decided to check the nook thread. Finally BN apps gone . Thank You
hi all, anyone have test factory reset on nstg US ? my backup is corrupt.
Envoyé depuis mon GT-N7100 avec Tapatalk
I'm wanting to backup all my apps and data on my Note 8.0 3G. (I would like to back everything up to an external drive).
My device is rooted, and most apps are saved to SD, as is described here:
http://forum.xda-developers.com/showthread.php?t=2276193&page=2
I also have Multi Window Manager Pro if that makes any difference.
And I have Titanium Backup Pro installed... But I have no idea how to use it.
Oh, and I have a USB OTG to USB adapter, so I can plug in an external drive no problem.
Please help! :fingers-crossed:
Just load up Titanium Backup ( The free version is also installed right? ) and touch the arrow in the upper right hand corner. It will then give you a list different backup scenarios to choose from. I use Backup new user apps & newer versions.
You can also change to backup to external sdcard in Preferences using the menu button.
kable said:
Just load up Titanium Backup ( The free version is also installed right? ) and touch the arrow in the upper right hand corner. It will then give you a list different backup scenarios to choose from. I use Backup new user apps & newer versions.
You can also change to backup to external sdcard in Preferences using the menu button.
Click to expand...
Click to collapse
Ok, so I managed to change the backup folder to a location I liked.
I selected the same option as you... and it takes me to a screen with the title 'Backup new user apps & newer versions'
Then 3 buttons: Select all, Deselect all, Invert selection.
then 'Pause active apps' and 'exclude active apps'.
then nothing else, no list of apps.
I tap the green tick, and I immediately get a notification that backup has finished. ....?
Edit: In other words, nothing happens - I check the folder and it's empty.
did you buy a license or is it the free version?
Go to their website and read up on how to use the software properly..
http://matrixrewriter.com/android/
https://play.google.com/store/apps/...wsMSwyLDEsImNvbS5yb290dW5pbnN0YWxsZXIucHJvIl0.
There is this app to make a backup of your applications....
wase4711 said:
did you buy a license or is it the free version?
Go to their website and read up on how to use the software properly..
http://matrixrewriter.com/android/
Click to expand...
Click to collapse
I installed the free version, then bought the licence. So yes, I have the Titanium Backup PRO/Donate version.
I went to the site and read the FAQ, Troubleshooting, and User Guide.
I also clicked the 'Problems' Button. Makes no difference... So I also upgraded Superuser to Superuser Elite for good measure.
Today, I am getting warning messages that weren't coming up yesterday... for instance:
When I choose the backup location on my external drive, the Overview page tells me my Backup directory is X not available.
when I click the page+arrow symbol on the top right, i get this message: 'The current backup location ("/storage/UsbDriveA/Stuff you DON'T WANT/N5100 Backup") cannot be accessed.'
Also, if I change the backup location to what it was originaly I get exactly the same problem: - Backup directory is X not available.
("/storage/sdcard0/TitaniumBackup") cannot be accessed.'
Looking at the Overview page, at the bottom, it says:
System ROM: 2.64 GB (958 MB free)
Internal+Media 10.6 GB (7.63 GB free)
Ext. SD card: 10.6 GB (7.63 GB free)
(I actually have a 64 GB MicroSD installed)
Do you know what I think is going on? TitaniumBackup is getting confused because of the script I have enabled to install apps to SD as is described here: http://forum.xda-developers.com/showthread.php?t=2276193
Which I did mention and link to in my first post. Are none of you using this method?
looks as if your internal card is mounted as external, and your removable card is not mounted. Are you running civato's kernel? if so, the vold entry in your mount script needs to be changed.
roustabout said:
looks as if your internal card is mounted as external, and your removable card is not mounted. Are you running civato's kernel? if so, the vold entry in your mount script needs to be changed.
Click to expand...
Click to collapse
I'm using the stock kernal. I haven't flashed a custom rom... All I've done to my device is this:
1 Install framaroot
http://forum.xda-developers.com/atta...0&d=1368232060
2. Open frama root and select SupesSu. Select the Aragorn method.
3. Reboot your device
4. Install busy box and open the app. Grant Su permissions and do the smart install
https://play.google.com/store/apps/d....busybox&hl=en
5. Now you are rooted and ready to follow the steps of this thread.
6. Use ur device to format the SD card
7. Download script and save to SD card
http://downloadandroidrom.com/file/G...e2/app2sdNote2
8. Install script manager from play store
9. Open script manager, click on browse as root then ok
10.Choose the downoaded file and choose Script/Executable
11. Now tap on Su, Boot and Save
12. Reboot your phone
Click to expand...
Click to collapse
And this is the script:
the script:
-----------------------script starts next line
#!/system/bin/sh
# extsd2internalsd is a modification that allows to switch internal sd to external sd
# and viceversa. With this you can use default internal sd only for app storage
# and the external sd to store all apps resource and all others stuff. The resut is a very
# big increase of installable apps on gnote2 and note8
# All credits to Mattiadj of xda forum for the idea and script and to mike1986 for
# the cmw zip. xda thread url at
# http://forum.xda-developers.com/show...php?t=2036796:
sleep 10
mount -o remount,rw /
mount -t vfat -o umask=0000 /dev/block/vold/179:17 /storage/sdcard0
sleep 30
mount -o bind /data/media /storage/extSdCard
chmod 777 /mnt/extSdCard
sleep 10
chown 1023:1023 /storage/extSdCard
chown 1000:1000 /storage/sdcard0
------------- end script on blank line above
Click to expand...
Click to collapse
Your script looks like it's doing what mine does.
When you use the settings control panel to look at storage, does your storage show that internal storage is larger than your SD card - in your case, it'd be ~60 gig internal and ~9 for sdcard?
If they show the same value (the value Titanium reports) there's a problem with your script. otherwise you should be ok as long as the folder exists.
I just checked my device and titanium shows what yours does - both memory pools are the same size. mine works fine and uses this path:
/storage/sdcard0/titanium
roustabout said:
Your script looks like it's doing what mine does.
When you use the settings control panel to look at storage, does your storage show that internal storage is larger than your SD card - in your case, it'd be ~60 gig internal and ~9 for sdcard?
If they show the same value (the value Titanium reports) there's a problem with your script. otherwise you should be ok as long as the folder exists.
I just checked my device and titanium shows what yours does - both memory pools are the same size. mine works fine and uses this path:
/storage/sdcard0/titanium
Click to expand...
Click to collapse
Yes, my internal storage is much larger (59.47Gb) - showing it is using the SD card, with the 'SD' (external) showing just under 10Gb.
I've restarted my device a couple of times, so I'm not getting those error messages. I can set my backup folder to the same as yours '/storage/sdcard0/TitaniumBackup', and I can also set it to the folder I want to use on my external drive - '/storage/UsbDriveA/Stuff you DON'T WANT/N5100 Backup'.
The problem now is that when I try to do a backup, selecting either 'Backup new user apps & newer versions' or 'Backup new user+system apps & newer versions' I'm presented with a screen where I'm supposed to select or deselect apps, but NO apps are listed! Not a single one.
What happens for you?
Titanium launches, confirms it has root rights and sqlite support, nags me if I happen to have USB debugging off, then lands at Overview.
I click on the Backup/Restore tab and it shows me a list of apps available to back up. If I click the checklist button, I get to "Batch Actions - ALL" and it tells me how many apps it's ready to back up, in my case 142 user apps.
The only thing that behaves as you're describing is if I've accidentally set a filter which doesn't match anything.
In the "Backup/Resore" tab there's a "Click to edit filters" button; if you go in there and there's a value set, try clearing it and then clicking the green checkmark to save your change. If you don't click the checkmark, your change isn't saved.
That may take you back to the backup/restore fully populated with user and system apps if you'd accidentally set a filter.
roustabout said:
The only thing that behaves as you're describing is if I've accidentally set a filter which doesn't match anything.
In the "Backup/Resore" tab there's a "Click to edit filters" button; if you go in there and there's a value set, try clearing it and then clicking the green checkmark to save your change. If you don't click the checkmark, your change isn't saved.
That may take you back to the backup/restore fully populated with user and system apps if you'd accidentally set a filter.
Click to expand...
Click to collapse
YES!!! For the strangest reason, I had it filtering out everything except 'flashbarservice.apk' which doesn't even exist on my device. :silly:
Thanks for identifying where the problem was. I must have accidentally saved that as a filter back when I was setting up my device and completely forgot about it. *slaps forehead*.
What a run around for such a simple obvious mistake.
Everything is now backing up nicely to my external drive. :good: :fingers-crossed:
***SOLUTION FOUND! I CAN NOW ACCESS THE FOLDER. SEE POST BELOW.***
Android File Transfer was working great up until a few days ago when it started to bug out, only for when trying to access the Camera folder on my exSD Card.
I can access everything else except when clicking on this folder the message pops up, which makes no sense because my screen isn't locked. (Screenshot attached.)
Could it be that the amount of pictures/videos on the exSD card is too much to handle for AFT? After all, it is a 64GB card...which is a lot of land to cover and load....hmmmm
I've tried this, but no luck.
Note: I'm aware of AirDroid etc...Personally I prefer to be plugged in direct via USB.
iunlock said:
Android File Transfer was working great up until a few days ago when it started to bug out, only for when trying to access the Camera folder on my exSD Card.
I can access everything else except when clicking on this folder the message pops up, which makes no sense because my screen isn't locked. (Screenshot attached.)
Could it be that the amount of pictures/videos on the exSD card is too much to handle for AFT? After all, it is a 64GB card...which is a lot of land to cover and load....hmmmm
I've tried this, but no luck.
Note: I'm aware of AirDroid etc...Personally I prefer to be plugged in direct via USB.
Click to expand...
Click to collapse
Not really a theme Or app question but I'll give it a swing.
Can you access it on your phone fine?
Did you try using a card reader an see if you can access it that way?
If it's stating locked, it may have set permissions on your folder that inhibit access? Check those in a root explorer an see what they say too
Sent from my SM-N900T using Tapatalk 2
Mod, can you move this over to the proper forum. Thanks.
Possible causes / Things I've tried:
I do have some pictures in an App called: KeepSafe, where you have to enter in a pin code to access those pics, so then I was thinking maybe this was causing the problem. So I entered the App and tried connecting, but darn...same old thing. Doesn't work and I keep getting the same error message as the pic I have attached to the original thread.
I have also tried to reboot in Recovery (twrp) and tried to mount the exSD, but still nothing. Here's the message it gave me:
E: Unable to mount '/usbstorage'
This is driving me crazy. Anyone?
cbucz24 said:
Not really a theme Or app question but I'll give it a swing.
Can you access it on your phone fine? - Yes I can access it just fine through ES File Explorer. I've also checked the permissions.
Did you try using a card reader an see if you can access it that way? - I'm sure it'll work fine with a card reader, but that's not my preferred method. It's just frustrating for something to have worked and out of the blue stop.
If it's stating locked, it may have set permissions on your folder that inhibit access? Check those in a root explorer an see what they say too - I've uploaded a screen shot of the message that I'm receiving.
Sent from my SM-N900T using Tapatalk 2
Click to expand...
Click to collapse
Try moving the KeepSafe files to another directory.
Frank
Update 6/30/14
SUCCESS!
From the gallery on your phone, you can create folders and move (not copy) over pictures/videos and it'll be default save it to your phones internal SD card.
I didn't want to move all 4,000+ pics/vids so I just did it in little batches of 20 here 50 there and made just a few folders.
Then I connected the phone to my computer and accessed the Camera folder and....bam there it OPENS!
My theory:
If you have more than ~50% of your external SD card filled up then chances are your computer (Android File Transfer, for Mac users) will have a hard time trying to access that huge folder that is < 30+GB's ...
Therefore, you just have to lighten up the load on that folder so that it can be accessed with ease...
Pretty straight forward and simple.
Update 6/30/14
***SOLUTION FOUND! I CAN NOW ACCESS THE FOLDER. SEE POST BELOW.***
From the gallery on your phone, you can create folders and move (don't copy) over pictures/videos and it'll by default save it to your phones internal SD card.
I didn't want to move all 4,000+ pics/vids so I just moved about a couple hundred pictures to varies folders.
Then I connected the phone to my computer and accessed the Camera folder and....bam there it OPENS!
My theory:
If you have more than ~50% of your external SD card filled up then chances are your computer (Android File Transfer, for Mac users) will have a hard time trying to access that huge folder that is < 30+GB's ... (Windows wouldn't open it either.)
Therefore, you just have to lighten up the load on that folder so that it can be accessed with ease...
Pretty straight forward and simple. Hope this helps.
iunlock said:
My theory:
If you have more than ~50% of your external SD card filled up then chances are your computer (Android File Transfer, for Mac users) will have a hard time trying to access that huge folder that is < 30+GB's ...
Click to expand...
Click to collapse
It is more likely that they thought it very unlikely that there would be more than the old limit of 2,000 files in a directory so they didn't allow for it in the program code.
Frank