Related
Now introducing: webtop2sd!
Please don't post in this thread if you happen to catch it when it's open - I'd like to keep it clean if possible. Discussion threads:
Motorola Atrix/Olympus + general
Motorola Droid Bionic/Targa
Motorola Photon/Sunfire
Index:
Main (this post!)
Changelog
Screenshots
Instructions
Partitioning Instructions
Known Issues
Major features:
As the name implies, you can now use your SD card as your Ubuntu disk. No more relying on a wimpy filesystem.
Since this uses a separate partition, you can still export your filesystem to your desktop.*
As a native** Android application, no more worrying about how to run a script. Just download the .apk, install, then run.
Taking it a step further, you can now boot from external storage as well. If you put your phone into USB host mode (such as via the lapdock), you can boot from any external USB drive. As a nifty note, this means that you can actually have multiple Ubuntu partitions lying around for testing purposes. Particularly useful for me! (Not working yet!)
Allows selection of various source and target partitions (so you can use this to create an Ubuntu partition, then use that new partition as a source for a testing partition if you so choose).
Now has an uninstall feature (but why would you want to? ).
Serves as the first of two applications. The other is a Python/Gtk program that will run within webtop to allow for configuration within the proper environment.
* Unfortunately, anything that can mount extfs (e.g. Linux) will still try to mount the Ubuntu filesystem, potentially causing double-mounting issues.
** Mostly native Android application, really, since it's performing several shell calls on the backend. But I'm sure you won't notice.
Other features:
If you don't have the ability/desire to partition and format your SD card first, webtop2sd can take care of that for you.
webtop2sd can also:
Delete an ubuntu.disk if you have one, freeing up space on your /data.
Disable TOMOYO Linux (mandatory access control).
Permanently fix /etc/mtab (which tends to become stale over time). Atrix and Photon only.
Grant sudo access.
Install a modified dock. Atrix and Photon only.
Tested hardware:
Motorola Atrix
AT&T
4.1.57
4.1.83
4.5.91 (1.1.0)
SmarTone-Vodafone
4.5.2 (a.k.a. the HKTW build) (0.9.1)
Motorola Droid Bionic
Verizon
5.5.886 (2.0.0)
Motorola Photon
Sprint
4.5.1A (2.0.0)
End User License Agreement:
Due to the amount of time and effort I've put into this project (at least an order of magnitude more than the Ubuntu batch files, as I've been working on it for several months), I've implemented an end user license agreement (EULA) on webtop2sd, although I've tried to make it as sane and readable as possible. I know many of you won't care, and many of you will ignore it, but it still felt like the appropriate thing to do in this situation. So that you can take a look at it prior to downloading:
By using webtop2sd, you agree to the terms of this End User License Agreement (EULA). If you do not agree with this EULA, uninstall and remove all copies of it (you can reject it by hitting Home and killing the application).
You are free:
to Use - execute this piece of software.
Under the following conditions:
Noncommercial - You may not use this software for commercial purposes.
Nondistributive - You may not distribute this software.
No Derivative Works - You may not disassemble, distribute, alter, transform, or build upon this software.
With the understanding that:
Waiver - Any of the above conditions can be waived if you get permission from the copyright holder.
Ownership - Use of this software does not grant ownership of any kind.
No Warranty/Liability - The author has done his best to write the software, but ultimately, you are responsible for anything that results from usage of the software.
Nonseverable - If any part of this EULA is deemed invalid, the rest of it still applies.
In case you are wondering, yes, this is patterned after the Creative Commons licenses.
As a result, xda-developers (specifically, this thread) is the only place you should be downloading this application. Which is conveniently attached below for your downloading pleasure.
Thanks:
eval-, for pointing out that it's possible to create a device during bootup if the system hasn't done it yet (which allowed for this endeavor to even take place!).
YellowGTO, for helping to debug the Atrix SmarTone-Vodafone build.
Brandon15811, for pointing me at the Ubuntu archive.
tallnerd1985, for lending me a Droid Bionic to port webtop2sd to.
distaula, for providing some of the details for and testing the Motorola Photon.
Lokifish Marz, for helping to test the Motorola Photon.
P.S. If you're wondering why there's an icon.zip attached, that's due to GPL requirements. You can safely ignore it, since it's just a svg of the icon.
Changelog:
2.0.1 (October 9, 2011):
Tweak webtop-configurator for the Photon's sources.list.
2.0.0 (October 8, 2011):
Multi-device support.
1.1.2 (October 2, 2011):
Fix busybox pathing issues.
1.1.1 (October 2, 2011): Long overdue bugfix:
Use busybox from /system if present.
1.1.0 (July 24, 2011): Gingerbread update:
If busybox is not present (*cough* Gingerbread *cough*), install it in /system/etc/webtop2sd so that the webtop2sd mount application can run properly.
Add a Diagnostics tab. At the moment, it shows this information:
webtop2sd version
Mount executable version (and corresponding source)
Whether or not the webtop2sd busybox is installed
The webtop configurator version
Currently mounted webtops
Add a "Reinstall mount executable" button.
Fix the "Install webtop configurator" button and rename it to "Reinstall mount executable".
With the increasing number of buttons, landscape mode on the Execution tab is becoming unusable. So, hide buttons when executing (except for one that makes it obvious that it's executing).
Expand the target tree in webtop configurator by default to make it more clear what options are available.
Swap over to using old-releases.ubuntu.com instead of jp.archive.ubuntu.com.
When rotating within webtop2sd, tab state is no longer lost.
When installing webtop configurator, don't choke if the /usr/local/share/pixmaps already exists.
1.0.0 (July 10, 2011): First "real" release:
webtop configurator now bundled.
Uninstallation implemented.
Workaround added for looping dock segfaults.
webtop2sd (the Android application) no longer has a reliance on busybox.
0.9.1 (June 29, 2011): Miscellaneous bug fixes:
Fixes for SmarTone-Vodafone 4.5.2.
Devices below 1 GB are no longer listed for partitioning.
If a target partition for synchronization isn't selected, synchronization won't be attempted.
The progress bar can now handle device rotation without losing state.
There is now a reminder to reboot after synchronization.
0.9.0 (June 26, 2011): Implementation of 95% of the final featureset. Partitioning and synchronization are no longer mutually exclusive operations.
Dropped features (deemed as a better fit for the companion program):
Fix Ubuntu packages
Fix APT source lists
Restrain APT dependencies
Known problems:
Boot from sd* not working.
Uninstall not working.
Companion program not written yet.
0.5.0 (June 11, 2011): UI prototype, although the UI should be fully functional (i.e. all menus should show accurate information). Of course, clicking on the "Go!" button doesn't actually do anything....
Screenshots:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
The partitioning tab.
The partitioning tab: device selection. The program will create two partitions on the device: one FAT, one ext3 (for webtop). The FAT partition will be the first, the ext3 partition the second.
The partitioning tab: partition size. Here, you can select how large you want the webtop partition to be.
The locations tab, where you pick source and destination partitions for synchronization.
The locations tab: source selection. Source webtops include the (now deprecated) filesystem files. External storage partitions are also valid too. If the source is a filesystem file, it can be automatically deleted upon successful completion of synchronization.
The locations tab: target selection. Destination partitions can include partitions generated as a result of partitioning.
More Screenshots:
The advanced tab. This is reached via the "Toggle Advanced tab" option on the menu. The specific options are discussed in the instructions.
The diagnostics tab. This is reached via the "Toggle Diagnostics tab" option on the menu. Information shown here can be used to determine the state of webtop2sd.
The execution tab. Several different actions can be performed from here.
The execution tab: execution. A progress bar is shown for the synchronization task, to show an approximation of how much is left.
Requirements:
A supported device with webtop (e.g. a Motorola Atrix/Olympus, a Photon/Sunfire, a Droid Bionic/Targa).
Some type of external storage. At the moment, webtop2sd can only boot off a microSD card, though, so that's probably your best option.
At least a partially functional webtop. The following executables are called:
/bin/umount (because it can unmount by device)
/sbin/mkfs.ext3
/sbin/blockdev
/usr/bin/dpkg-deb
/usr/bin/file
Instructions:
Note: webtop2sd scans devices and partitions upon startup, so if you change out SD cards and/or USB devices once it's launched, you'll need to forcibly close the application and re-launch it.
You will need a partitioned device, so that's the first tab shown, Partitioning. Performing partitioning via webtop2sd is destructive, so it will warn you appropriately. Non-destructive partitioning can be performed, and those instructions are below. If you still want to partition your device, follow these instructions:
Enable partitioning external storage by turning on the checkbox for "Partition ext. storage".
Select the target device by hitting "Device to partition". MicroSD cards are appropriately labelled as "SD card", and correspond to the mmcblk1 device. External storage is labelled as such, and correspond to sd* devices. The size of the device is marked in parentheses. Any device you have selected should be unmounted from Android first (although webtop2sd will detect if you've selected the microSD card, and send you to the appropriate Settings page - I haven't figured out the exact syntax to send users to the Blur device ejection dialog box).
Once you've selected a device, hit the "Webtop partition size" option to determine how large the webtop partition should be. The minimim size is 1 GB (1,024 MB).
Advanced options:
Format new partitions: If you turn this off, the partitions won't be automatically formatted after partitioning, but this will cause problems with synchronization if you have that enabled.
Once partitioning is set up, webtop synchronization can be configured in the Locations tab.
The "Generate a webtop" box is checked by default.
Select a source partition via the "Source webtop" option. It should always show "Internal flash" (mmcblk0p13) as an option unless something is horribly, horribly wrong. The "Filesystem file" (/data/ubuntu.disk) option will be shown if you installed a previous custom Ubuntu system. Any other extfs partitions labelled "osh" will be shown as valid source partitions as well, unless partitioning is active and the partition is on the device to be partitioned.
Similarly, select a target partition. All extfs partitions are shown as valid target partitions, unless partitioning is active and the partition is on the device to be partitioned, or that partition has already been selected as the source partition. If partitioning is active, however, an entry is automatically entered.
If the "Filesystem file" option is selected as a source partition, it can be automatically deleted on a successful synchronization, so that the space occupied on /data can be freed up.
Advanced options:
Replace mount executable: An alternate mount executable is required if you want to boot a custom webtop. However, if you've tweaked the one you already have to work the way you want, you can uncheck this box.
Install busybox if needed: The alternate mount executable needs certain Unix commands to run properly. These were provided via busybox in 2.2/Froyo, but were removed in 2.3/Gingerbread, so webtop2sd is able to reinstall busybox in /system/etc/webtop2sd if needed.
Disable TOMOYO Linux: Highly recommended, as TOMOYO Linux mandatory access control can cause many problems down the road. In theory, it's not strictly required, as webtop2sd shouldn't trigger any changes that would cause TOMOYO to be unhappy, but it allows for the user to easily perform actions that would do so. So rather than making TOMOYO unhappy, it's preferable to effectively disable it (desu wa). But, if your TOMOYO configuration files (domain_policy.conf and exception_policy.conf) are already set up, you can uncheck thix box.
Fix /etc/mtab: This addresses a personal pet peeve of mine. /etc/mtab, which is supposed to keep track of the list of current mounts, doesn't get cleaned up properly, so can end up with a number of dead entries (seen when running "mount" to see a list of current mounts). It doesn't actually break anything per se, but it's ugly. Replacing it with a symlink to /proc/mounts fixes everything. Atrix and Photon only.
Missing dock workaround: If the AWN dock doesn't show up when you boot into your SD webtop, run webtop2sd with this enabled (it's disabled by default). Atrix and Photon only.
Grant sudo access: Moving webtop to external storage doesn't accomplish much if it can't be subsequently configured and improved upon. This can be difficult without some easy form of root access, and granting "sudo" access to the "%admin" group (which includes the webtop user, "adas") does exactly that. However, if your sudoers file is already set up exactly the way you want, you can uncheck this box.
Install modified dock: Similar to the above, moving webtop to external storage doesn't accomplish much if you have no additional options. So, if you're coming from the stock webtop installation, a modified dock can be installed to give you some more functionality to start with. Atrix and Photon only.
Once all options have been configured, you can head to the Execute tab and hit the "Go!" button. You can keep track of status via this tab. An "Executing..." item is added to the Ongoing Notifications section so that Android won't automatically kill webtop2sd.
If you're finding that the partitioning and formatting appear to be taking an inordinately long time, you can perform that on your computer (as described below) and then have your device only perform the synchronization.
After the program completes, reboot your device to use your new webtop.
Once you've rebooted, run the webtop configurator. Atrix and Photon only. It tends to be slow because it does a lot of network operations without revealing what it's doing.
When you first launch it, you'll probably see a screen where it says it needs to update the APT sources list. This can take a while.
At the moment, only two programs are supported (both under APT/Administration): LXTerminal and Synaptic.
Partition Instructions:
Depending upon your operating system, free software may be available so that you can partition and format your device without losing all the data on it. When you partition it, I recommend that you have your FAT32 partition first, and any extfs partitions later. I would also recommend using ext3 as your extfs filesystem type (the Olympus kernel doesn't support ext4, so any potential benefits it could offer are lost).
Linux: gparted (you probably already have this installed)
Mac OS X: ?
Windows: MiniTool Partition Wizard
Warning: If you're worried about the number of write cycles on your SD card, you're probably best off copying all the data off, partitioning, then copying all the data back, as repartitioning tends to hit your SD card pretty heavily. That said, I personally am not worried, but it's your respective calls on this one.
Instructions: Windows
Those of you using Linux probably have a pretty good idea of how to use gparted, so I'll skip those for now. Here's a quick runthrough for Windows on how to partition your SD card. You'll need an SD card reader, of course.
If you take a look at your SD card in Computer Management/Disk Management, you'll have doubtless noticed that you don't have the traditional partitioning options available there that are there for "proper" hard drives.
So we'll need to use a different tool - in this case, the MiniTool Partition Wizard mentioned above.
This is what my MiniTool Partition Wizard screen looks like when I have an 8 GB SD card inserted. As you can see, there's currently one single FAT32 partition present.
When you right click on the partition, you'll see a Move/Resize option. That's the one you want to select for non-destructive partitioning.
At that point, you can select how large you want your partition to be. You want to make sure that the "Unallocated Space Before" stays at 0.00 MB, so that the new partition will be the second one. In my case, I've opted to create a 4 GB partition as the second partition.
Once that has been set up, right click on the Unallocated space, then select Create.
We're not worried about the warning that Windows throws up, particularly since we know we'll be creating a partition that Windows can't read anyways. So just hit Yes.
Create the second partition at the maximum size with the following settings:
Create As: Primary
File System: Ext3
After that's done, click on the Apply Changes button.
And now you're done! Put the card back into your Motorola Olympus.
Known webtop2sd Issues:
Major:
On some devices, the AWN dock can go into an infinite segfault loop. (Partially fixed in 1.0.0, "proper" fix pending?)
The companion Python/Gtk program doesn't exist yet. 1.0.0
The "Install webtop configurator" button does nothing. 1.1.0
webtop2sd is unable to boot from an SD card without busybox. 1.1.0
Moderate:
External storage other than the microSD card can't be used as a boot device.
Detection of root privileges doesn't work properly.
busybox is only ever detected from /system/etc/webtop2sd. 1.1.1/1.1.2
Uninstallation isn't implemented. 1.0.0
It's not always easy to find out which webtop partitions are currently being used. 1.1.0
Minor:
Localization? Should be easy, since everything is stored in appropriate resource files....
You can selected devices to partition that are smaller than 1 GB. 0.9.1
If no target partition is selected (i.e. the option is greyed out), you can still try to generate a new webtop partition. 0.9.1
Known webtop configurator Issues:
Major:
What the hell is webtop configurator doing?! Status is a must.
Moderate:
jp.archive.ubuntu.com isn't an ideal mirror to pull from. old-releases.ubuntu.com is a better choice. 1.1.0
Minor:
Having the selection tree on the left fully expanded on boot would be nice, so that it's immediately obvious what options are available. 1.1.0
Enabling swap may add some virtual memory to your sdcard, but it may reduce the performance and speed
the objective of this how-to is to get everybody to know how they can enable swap with the help of a file on their on
swapper 2 application will do this in a much better way and it would be an automated process
this post is only for knowledge purpose
the recommendation is to use "swapper 2" available in play store
Steps:-
1. open any file manager and create a folder called "swap"
2. open that folder and create an empty file called "swap"
3. now open Terminal emulator and type
Code:
mkswap /sdcard/swap/swap [B]amount in KB[/B]
the amount in KB is the size of the swap file in the KB unit that you want to create
in other words the the amount of additional virtual memory you want to add
Click to expand...
Click to collapse
normally amount in KB should be equal or more to your current RAM
creating the swap file may take ~2 minute
4.now type in terminal
Code:
swapon /sdcard/swap/swap
the above command will activate the swap
5. now we will set the swappiness, for that purpose another command needs to be put in the terminal that is
Code:
echo 100 > /proc/sys/vm/swappiness
4th and 5th steps are needed to run after every reboot so for that purpose I have created a script just download it and set it to run on boot in script manager or put it in init.d if you have it, you can download script from here
now everything is set just put busybox free and see if you get swap working or not
any doubt please ask
not found
i enter it in terminal :
mkswap/sdcard/swap/swap 1048576
badnamess said:
i enter it in terminal :
mkswap/sdcard/swap/swap 1048576
Click to expand...
Click to collapse
use "space" after mkswap..
Swapon failed on /sdcard/swap/swap
Hi,
I'm trying to create and delete zip files through command on external SDCard, but fails. The 'Permission denied' message is shown when both commands are executed.
I have tested it on latest Tasker beta version, and also using Terminal app, but as it would be obvious, same error is shown.
I know that I can use Tasker's built-in actions on (+ > File), but I want to use commands.
Details:
• OS: LOS 14.1 (N 7.1.2) rooted
• cmd: rm /storage/xxxx-xxxx/BACKUP/Apps/Tasker/*.zip
Note: If you ask if I granted Document Tree Access one to Tasker, I did.
As ive written in my past posts, using exagear (windows emulator based on wine), before I try to give that one su and read external sd and make final attempts to read more than 1 folder... im trying to bind folders. from terminal on phone. I did it with ADB and usb connected to PC with bindfs, I make a bind between Download\ and folder on external SD card, it is read by Exagear as it sees the External folder instead of the actual Download folder. But the moment I disconnect from PC or disable ADB debugging, the bind is lost, Download folder even disappears, have to reboot to restore folder.
Im using Magisk to give any such app su. So I give SU to terminal emulator apk and when I perform the same bindfs command it binds the 2 folders but only in the terminal. If I browse the folders with file explorer I won't see the External SD folder when going to Download'\ and neither will the exagear (unlike when done from ADB). So I need to bind them when away from PC, so I can 'see'the external sd
Tried FolderMount apk, few others, commands, which one works to properly bind as can be seen in all apps or particular? My final stop will be to try reverse engineer and see if su will allow exagear to see more than 1 folder (it only sees Download folder)
FBind Magisk module: (read last pages)
https://forum.xda-developers.com/apps/magisk/module-magic-folder-binder-t3621814
Rclone Mount Magisk module (on repository). Check the use of rclone with local storage.
Also the apps Apps2sd (by Vicky Bonick, see thread on XDA), Folder Mount, Luc* Pat* (ignore the piracy side of it, it has some nice other features) and maybe others can bind folders (may not work fine on some Android versions).
Ok I try fbind module, how do I use it? i installed the module in Magisk 20.4 and now i need the correct syntax. I tried
PHP:
fbind <external sd path> storage/emulated/0/download>
andit throws me into the menu
1) non_media_to_external 5) documentation
2) media_to_external 6) all_commands
3) obb_to_external 7) exit_wizard
4) troubleshooting 8) boot_log
--> OPTION <enter>:
Which one to do what I want /mnt/media_rw/MD6H-KDY5/My\ Folder /mnt/runtime/write/emulated/0/download
where the first folder is a folder on external sd that has to be mounted as download folder
ALSO I cant remove something, I created mnt/runtime/read/emulated/0/mnt/media_rw/MD6H-KDY5/My Folder and mnt/runtime/read/emulated/0/mnt/runtime/write/emulated/0/download
(oops partially solved this as explained here by enabling core only module in Magisk manager, reboot phone then they can be deleted). But then they are back if i allow fbind modules.. Final solution was to put (overwrite) some empty config.txt in data/adb/fbind and then I can delete the folders, it seems to read it from there. So no need to switch to Core only in magisk or uninstall the fbind.
It is why I need to do this correctly to not make a mess
OK did it with bindfs as I explain in other thread and important to do is in Magisk Settings in Mount Namespace Mode set it to Global, then use ScanMediaPlz apk or without it, reboot phone and retry again command in Terminal and see if external SD content will be on the Download folder
Hi
Since no one reads this bit of the OP, let's get to it. Credit to Cloudxddd for posting the sd card fix in another thread.
Enable ADB shell
On your Tablet:
Open the settings app
Scroll down to 'About tablet'
Select 'Software information'
Continuously tap on 'Build number' over and over until at the bottom of the screen you see a toast saying "Developer mode has been enabled"
Go back to the main settings page and scroll down, select the new 'Developer options' button
Enable 'USB debugging' (press OK to confirm)
On Ubuntu:
Install ADB: sudo apt install adb
Plug your tablet into your PC via USB
Start ADB and check your device is connected: adb devices (if more than one device is listed, unplug your second android phone/tablet
You may need to approve the connection on your tablet
Run ADB shell: adb shell
Remove stock apps (bloatware)
In ADB shell (see above):
List the apps installed: pm list packages
Removing some apps will cause your tablet to brick (fixed by doing a factory reset from the recovery menu), so be careful
Search APK Mirror for the package name if you don't know what app you're looking at
To uninstall an app from your user but keep it on the device: pm uninstall -k --user 0 <packagename>
Reboot the device to ensure it can boot successfully: reboot
Reply below with the apps you removed and whether it was successful / safe
Reinstall that app: cmd package install-existing <package name> (or do a factory reset if it failed)
Completely remove the app and reclaim the space if you're certain it can be removed safely: pm uninstall <packagename>
Reboot the device to ensure it can boot successfully: reboot
Note: Some apps reinstall when you reboot.
Apps that might be safe to remove - Please reply with updates
Package nameApp nameSafe to remove?com.samsung.android.video
Samsung video playerYescom.samsung.android.app.dofviewer
com.samsung.android.app.siofviewer
Samsung live focus?
com.samsung.android.app.dressroom
Samsung wallpapers?
com.sec.android.widgetapp.webmanualSamsung user manualYescom.samsung.android.allshare.service.mediashareSamsung nearby service?com.samsung.android.app.clockpackSamsung clock style?com.google.android.apps.youtube.musicYoutube musicYescom.sec.android.app.bluetoothtestSamsung bluetooth test?
com.samsung.app.newtrimSamsung video trimmer?com.samsung.android.app.shareliveSamsung quick share?
com.samsung.android.scloudSamsung cloud?
com.samsung.android.stickercenterSamsung sticker center?
com.android.chromeGoogle chrome?com.google.android.apps.mapsGoogle maps?
com.google.android.apps.docsGoogle docs?
com.sec.android.gallery3dSamsung gallery?com.google.android.apps.tachyonGoogle DuoYescom.sec.android.app.soundaliveSamsung soundalive?com.microsoft.skydriveMicrosoft onedriveYescom.netflix.mediaclient
com.netflix.partner.activationNetflixYescom.google.android.youtubeYoutubeYescom.google.android.videosGoogle play movies and tvYes
Enable apps to SD
In ADB shell (see above):
List disks: sm list-disks
Partition the disk to be used entirely for apps to SD: sm parition <DISK> private
Partition a percentage of the disk to be used for apps to SD: sm partition <DISK> mixed <number>
Reboot: reboot
Open the 'Settings' app and and select 'Apps'
Select an app
Tap 'Storage'
Tap 'Change' to move it to the SD card (if the app supports this)
Thanks for this! will try today!
.
Hi,
Thanks for sharing. It does delete...but everytime i reboot it comes back...
lukyjay said:
Hi
Since no one reads this bit of the OP, let's get to it. Credit to Cloudxddd for posting the sd card fix in another thread.
Enable ADB shell
On your Tablet:
Open the settings app
Scroll down to 'About tablet'
Select 'Software information'
Continuously tap on 'Build number' over and over until at the bottom of the screen you see a toast saying "Developer mode has been enabled"
Go back to the main settings page and scroll down, select the new 'Developer options' button
Enable 'USB debugging' (press OK to confirm)
On Ubuntu:
Install ADB: sudo apt install adb
Plug your tablet into your PC via USB
Start ADB and check your device is connected: adb devices (if more than one device is listed, unplug your second android phone/tablet
You may need to approve the connection on your tablet
Run ADB shell: adb shell
Remove stock apps (bloatware)
In ADB shell (see above):
List the apps installed: pm list packages
Removing some apps will cause your tablet to brick (fixed by doing a factory reset from the recovery menu), so be careful
Search APK Mirror for the package name if you don't know what app you're looking at
To uninstall an app from your user but keep it on the device: pm uninstall -k --user 0 <packagename>
Reboot the device to ensure it can boot successfully: reboot
Reply below with the apps you removed and whether it was successful / safe
Reinstall that app: cmd package install-existing <package name> (or do a factory reset if it failed)
Completely remove the app and reclaim the space if you're certain it can be removed safely: pm uninstall <packagename>
Reboot the device to ensure it can boot successfully: reboot
Note: Some apps reinstall when you reboot.
Apps that might be safe to remove - Please reply with updates
Package nameApp nameSafe to remove?com.samsung.android.video
Samsung video playerYescom.samsung.android.app.dofviewer
com.samsung.android.app.siofviewer
Samsung live focus?
com.samsung.android.app.dressroom
Samsung wallpapers?
com.sec.android.widgetapp.webmanualSamsung user manualYescom.samsung.android.allshare.service.mediashareSamsung nearby service?com.samsung.android.app.clockpackSamsung clock style?com.google.android.apps.youtube.musicYoutube musicYescom.sec.android.app.bluetoothtestSamsung bluetooth test?
com.samsung.app.newtrimSamsung video trimmer?com.samsung.android.app.shareliveSamsung quick share?
com.samsung.android.scloudSamsung cloud?
com.samsung.android.stickercenterSamsung sticker center?
com.android.chromeGoogle chrome?com.google.android.apps.mapsGoogle maps?
com.google.android.apps.docsGoogle docs?
com.sec.android.gallery3dSamsung gallery?com.google.android.apps.tachyonGoogle DuoYescom.sec.android.app.soundaliveSamsung soundalive?com.microsoft.skydriveMicrosoft onedriveYescom.netflix.mediaclient
com.netflix.partner.activationNetflixYescom.google.android.youtubeYoutubeYescom.google.android.videosGoogle play movies and tvYes
Enable apps to SD
In ADB shell (see above):
List disks: sm list-disks
Partition the disk to be used entirely for apps to SD: sm parition <DISK> private
Partition a percentage of the disk to be used for apps to SD: sm partition <DISK> mixed <number>
Reboot: reboot
Open the 'Settings' app and and select 'Apps'
Select an app
Tap 'Storage'
Tap 'Change' to move it to the SD card (if the app supports this)
Click to expand...
Click to collapse
I've tried enable apps to sd . I've done everything as above and all seems to work but I still can't transfer any apps to sd card .
Johnseventythree said:
I've tried enable apps to sd . I've done everything as above and all seems to work but I still can't transfer any apps to sd card .
Click to expand...
Click to collapse
Yep, same. I split the card 50/50. After a reboot, the actual card even showed as only half the size. But there was just no button at all in any app´s storage settings. And I know what to look for! Because my thine actually has that exact button. To me this looks like Samsung just flat out disabled the feature.
I just hope someone comes up with an answer to samsungs mess up as the tablet is good . Would rooting the tablet make it so I could save apps to the sd card .
I did this on my Windows laptop. ADB wouldn't recognize the tablet until I downloaded the drivers from Samsung and installed them. I hadn't had to install anything other than the Google drivers until now.
grabber5.0 said:
I did this on my Windows laptop. ADB wouldn't recognize the tablet until I downloaded the drivers from Samsung and installed them. I hadn't had to install anything other than the Google drivers until now.
Click to expand...
Click to collapse
Oh rite could you possibly post a link to the drivers please. When I open ADB it shows the serial number of my table so I just thought all was OK but maybe installing the official drivers from samsung will solve this issue . Thanks mate .
Johnseventythree said:
Oh rite could you possibly post a link to the drivers please. When I open ADB it shows the serial number of my table so I just thought all was OK but maybe installing the official drivers from samsung will solve this issue . Thanks mate .
Click to expand...
Click to collapse
Here is the link for the Samsung USB drivers: https://developer.samsung.com/mobile/android-usb-driver.html
Without the drivers, ADB does not show the device at all, so I think you're fine.
grabber5.0 said:
Here is the link for the Samsung USB drivers: https://developer.samsung.com/mobile/android-usb-driver.html
Without the drivers, ADB does not show the device at all, so I think you're fine.
Click to expand...
Click to collapse
Oh right well I've done everything it says and nothing has changed I still don't have the option to save apps to memory card . I'll try the drivers and thankyou for the link . Why samsung has done this is beyond me ..
lukyjay said:
Hi
Since no one reads this bit of the OP, let's get to it. Credit to Cloudxddd for posting the sd card fix in another thread.
Enable ADB shell
On your Tablet:
Open the settings app
Scroll down to 'About tablet'
Select 'Software information'
Continuously tap on 'Build number' over and over until at the bottom of the screen you see a toast saying "Developer mode has been enabled"
Go back to the main settings page and scroll down, select the new 'Developer options' button
Enable 'USB debugging' (press OK to confirm)
On Ubuntu:
Install ADB: sudo apt install adb
Plug your tablet into your PC via USB
Start ADB and check your device is connected: adb devices (if more than one device is listed, unplug your second android phone/tablet
You may need to approve the connection on your tablet
Run ADB shell: adb shell
Remove stock apps (bloatware)
In ADB shell (see above):
List the apps installed: pm list packages
Removing some apps will cause your tablet to brick (fixed by doing a factory reset from the recovery menu), so be careful
Search APK Mirror for the package name if you don't know what app you're looking at
To uninstall an app from your user but keep it on the device: pm uninstall -k --user 0 <packagename>
Reboot the device to ensure it can boot successfully: reboot
Reply below with the apps you removed and whether it was successful / safe
Reinstall that app: cmd package install-existing <package name> (or do a factory reset if it failed)
Completely remove the app and reclaim the space if you're certain it can be removed safely: pm uninstall <packagename>
Reboot the device to ensure it can boot successfully: reboot
Note: Some apps reinstall when you reboot.
Apps that might be safe to remove - Please reply with updates
Package nameApp nameSafe to remove?com.samsung.android.video
Samsung video playerYescom.samsung.android.app.dofviewer
com.samsung.android.app.siofviewer
Samsung live focus?
com.samsung.android.app.dressroom
Samsung wallpapers?
com.sec.android.widgetapp.webmanualSamsung user manualYescom.samsung.android.allshare.service.mediashareSamsung nearby service?com.samsung.android.app.clockpackSamsung clock style?com.google.android.apps.youtube.musicYoutube musicYescom.sec.android.app.bluetoothtestSamsung bluetooth test?
com.samsung.app.newtrimSamsung video trimmer?com.samsung.android.app.shareliveSamsung quick share?
com.samsung.android.scloudSamsung cloud?
com.samsung.android.stickercenterSamsung sticker center?
com.android.chromeGoogle chrome?com.google.android.apps.mapsGoogle maps?
com.google.android.apps.docsGoogle docs?
com.sec.android.gallery3dSamsung gallery?com.google.android.apps.tachyonGoogle DuoYescom.sec.android.app.soundaliveSamsung soundalive?com.microsoft.skydriveMicrosoft onedriveYescom.netflix.mediaclient
com.netflix.partner.activationNetflixYescom.google.android.youtubeYoutubeYescom.google.android.videosGoogle play movies and tvYes
Enable apps to SD
In ADB shell (see above):
List disks: sm list-disks
Partition the disk to be used entirely for apps to SD: sm parition <DISK> private
Partition a percentage of the disk to be used for apps to SD: sm partition <DISK> mixed <number>
Reboot: reboot
Open the 'Settings' app and and select 'Apps'
Select an app
Tap 'Storage'
Tap 'Change' to move it to the SD card (if the app supports this)
Click to expand...
Click to collapse
Brilliant! I almost quit initially but then realized you spelled partition wrong.
List disks: sm list-disks
Partition the disk to be used entirely for apps to SD: sm parition <DISK> private
Partition a percentage of the disk to be used for apps to SD: sm partition <DISK> mixed <number>
But after that it still didn’t work. But I heard Rona cheering me on. Dug into the crates of Google and found this and it worked! I used AppMgr III to move the apps. I was able to move Amazon successfully.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
mydjtl said:
Brilliant! I almost quit initially but then realized you spelled partition wrong.
List disks: sm list-disks
Partition the disk to be used entirely for apps to SD: sm parition <DISK> private
Partition a percentage of the disk to be used for apps to SD: sm partition <DISK> mixed <number>
But after that it still didn’t work. But I heard Rona cheering me on. Dug into the crates of Google and found this and it worked! I used AppMgr III to move the apps. I was able to move Amazon successfully.
View attachment 5217751
Click to expand...
Click to collapse
mydjtl said:
Brilliant! I almost quit initially but then realized you spelled partition wrong.
List disks: sm list-disks
Partition the disk to be used entirely for apps to SD: sm parition <DISK> private
Partition a percentage of the disk to be used for apps to SD: sm partition <DISK> mixed <number>
But after that it still didn’t work. But I heard Rona cheering me on. Dug into the crates of Google and found this and it worked! I used AppMgr III to move the apps. I was able to move Amazon successfully.
View attachment 5217751
Click to expand...
Click to collapse
Amazing it worked flawlessly thankyou so much my daughters tablet has space again and she's not lost any of her apps . Respect to ya ....
mydjtl said:
Brilliant! I almost quit initially but then realized you spelled partition wrong.
List disks: sm list-disks
Partition the disk to be used entirely for apps to SD: sm parition <DISK> private
Partition a percentage of the disk to be used for apps to SD: sm partition <DISK> mixed <number>
But after that it still didn’t work. But I heard Rona cheering me on. Dug into the crates of Google and found this and it worked! I used AppMgr III to move the apps. I was able to move Amazon successfully.
View attachment 5217751
Click to expand...
Click to collapse
I followed these steps, and everything seems to work. Only some apps can be moved to the SD card, but that's not surprising.
However, after rebooting, Android decides that the app data is corrupted, and forces me into safe mode, from which a factory reset is the only solution.
So this only works for me if I never reset or power off the device.
Have to say, I'm never buying Samsung again. I've just had so many issues with this device. Even trivial stuff, like not being able to connect to Wifi via WPS when setting up the device (or when doing a factory reset)
After rebooting, I the tablet doesn't restart - it boots into Android Recovery, and the rescue summary shows I get NullPointerException: Attempt to invoke virtual method WindowManagerService.detectSafeMode() on a null object reference.
according to me, this method doesn't seem to work. i've got a 64gb microsd, followed the steps as indicated, after reboot the sd card shows up as "corrupted" and everytime a format is needed. unfortunately, moving apps to sd seems to be not possible. such a shame since the tab s7 can do it and this one not. hope that with android 11 update (if ever there will be) they enable this feature.
kitamurt said:
according to me, this method doesn't seem to work. i've got a 64gb microsd, followed the steps as indicated, after reboot the sd card shows up as "corrupted" and everytime a format is needed. unfortunately, moving apps to sd seems to be not possible. such a shame since the tab s7 can do it and this one not. hope that with android 11 update (if ever there will be) they enable this feature.
Click to expand...
Click to collapse
for me it works !
did you understand how adoptable storage works ??? no, then read this!
'adoptable-storage' tag wiki
Q&A for enthusiasts and power users of the Android operating system
android.stackexchange.com
i did the following and it works for me:
1. format your inserted SD-Card in the Tab A7 and dismount the SD-card after formatting
2. enable USB-debugging and connect with adb console to Tab A7
3. enter the following commands
Code:
adb shell
sm list-disks adoptable
i got the result
Code:
disk:179,32
my SD-card is 128GB size and i want 32GB (25% of total SD-Card)
for use as internal adopted storage
therefore i want 96GB (75% of total SD-Card) as external SD-card
to do this use the following commands (as adviced in posting #12)
Code:
sm set-force-adoptable true
sm partition disk:179,32 mixed 75
sm set-force-adoptable false
then i rebooted my Tab A7 and mounted the external SD-card (which shows 86,9GB)
the internal storage shows two items
1. internal storage 32GB
2. SD-Card adopted storage ( it doesnt tell you the adopted storage size but
it says 100GB used out of 128GB) which means 28GB are free for further usage,
at this point i have moved already all apps which are moveable to external storage.
i use the app "AppMgr III" as App 2 sd - utility
there are no errors or other problems after rebooting or during normal use.
it just works
hth
tiwag
tiwag said:
for me it works !
did you understand how adoptable storage works ??? no, then read this!
'adoptable-storage' tag wiki
Q&A for enthusiasts and power users of the Android operating system
android.stackexchange.com
i did the following and it works for me:
1. format your inserted SD-Card in the Tab A7 and dismount the SD-card after formatting
2. enable USB-debugging and connect with adb console to Tab A7
3. enter the following commands
Code:
adb shell
sm list-disks adoptable
i got the result
Code:
disk:179,32
my SD-card is 128GB size and i want 32GB (25% of total SD-Card)
for use as internal adopted storage
therefore i want 96GB (75% of total SD-Card) as external SD-card
to do this use the following commands (as adviced in posting #12)
Code:
sm set-force-adoptable true
sm partition disk:179,32 mixed 75
sm set-force-adoptable false
then i rebooted my Tab A7 and mounted the external SD-card (which shows 86,9GB)
the internal storage shows two items
1. internal storage 32GB
2. SD-Card adopted storage ( it doesnt tell you the adopted storage size but
it says 100GB used out of 128GB) which means 28GB are free for further usage,
at this point i have moved already all apps which are moveable to external storage.
View attachment 5261485
i use the app "AppMgr III" as App 2 sd - utility
there are no errors or other problems after rebooting or during normal use.
it just works
hth
tiwag
Click to expand...
Click to collapse
thx, found out that the sd card was not working correctly. tried with another one and worked flawlessly!
update: the method seems to be very unstable, if compared to app installed on internal memory. anytime i try to run an app, it's ok for 10-15 minutes, then suddenly blocks and reboots. this happens everytime and once rebooted, it will show that apps are not installed on ext sdcard; temporary fix when rebooted again, but it's very bothering.
FYI those methods work but are limited as you can't move certain apps or can't move their data sometimes.
If you're looking for even more space, I'd recommend App2sd (by Vicky Bonick, NOT the appMgr iii automatisation thing). You'll have to format your sd card with two partitions :
- one FAT32, that will be used as a "standard" sd card, visible by the device and all
- one F2FS, that will be used to link apps to sd card and will be invisible to most of the apps.
when asked to provide su.dpost-fs-data.d/service.d adress I used :
Code:
/data/adb/service.d
But, yes it requires root access. I'm still giving it a try but so far this is the only method that I've managed to move stuff like Genshin impact and its 8GB of data that somewhat disappear into thin air using other methods.
EDIT : after messing around for a few hours. This method is still not perfect ... I have troubles moving some obb files with it. But it's still worth a shot
tiwag said:
for me it works !
there are no errors or other problems after rebooting or during normal use.
it just works
hth
tiwag
Click to expand...
Click to collapse
Thanks, followed your guide and initially it worked correctly.
I also rebooted the table and it still worked.
However now (after a shutdown) the SD card is recognized as corrupt / damaged (translated).
It is still part of the adoptable storage.
I earlier reported it didn't work anymore after a reboot.
However checking a few days later it works again.
I guess it ran out of battery and rebooted.....
Thanks.
It works great on my SM-T500. I was able to use my 64GB SD Card as Device Storage. I was able to move Asphalt 8 game from Internal Storage to SD Card